Nothing here yet.
May 18 · 13 min read · In Part 5, we changed QuickBite to an event-driven design. Orders now writes an order and publishes an OrderCreatedevent, and Inventory processes that event later. This is a better design than direct
Join discussion
May 9 · 25 min read · In Part 4, we made Orders call Inventory directly using gRPC. That gave us a working flow, but it also showed a common problem like Orders has to wait for Inventory every time. If Inventory is slow, O
Join discussion
May 6 · 16 min read · In Part 3, we created the Inventory service and defined its API using gRPC and a .proto file. Both services were running locally, but they were still separate pieces. In this part, we connect them for
Join discussion
May 4 · 16 min read · In Part 2, we built the Orders service with proper folder structure, Postgres, migrations, and Docker Compose. That gave us a solid foundation. In this part, we will add the second service: Inventory.
Join discussion
May 1 · 19 min read · In Part 1, I explained what QuickBite is and what we are trying to learn. In this part, we build the first real backend service: Orders. This post follows the same structure as the final project we wi
Join discussion
