wheres-my-pizza by ymoldabe · Pull Request #13 · alem-platform/backend

ymoldabe · 2025-06-16T07:14:37Z

Добавил учебный проект wheres-my-pizza — трёхсервисное Go-приложение, построенное на RabbitMQ + PostgreSQL с шаблоном «Transactional Outbox / Inbox». Цель - показать, как реализовать надёжную event-driven цепочку Order Placed => Kitchen => Delivery с ретраями, DLQ и идемпотентной обработкой.

atlekbai · 2025-06-16T13:27:30Z

wheres-my-pizza/README.md

+## Guidelines from Author
+
+1. Tests first. Spin up PostgreSQL + RabbitMQ with Testcontainers-go and create unit/contract/e2e tests that should fail until each step is implemented.
+2. Implement database schema and outbox publisher.
+3. Wire minimal consumer in `kitchen`; emit `Boxed`.
+4. Add `delivery` with payment simulation.
+5. Introduce retry exchange & DLQ.
+6. Write e2e tests with **Testcontainers-go**.
+


Double-check что нужно использовать что нет

atlekbai · 2025-06-16T13:28:15Z

wheres-my-pizza/README.md

+- Event-driven architecture
+- RabbitMQ: work-queue, fan-out, dead-letter / retry queues, manual **ACK/NACK + QoS**
+- Exchange types & routing keys
+- Transactional Outbox pattern (**events** table) + PostgreSQL
+- Idempotent message processing (Inbox tables)
+- Docker-Compose orchestration
+- Unit, contract & end-to-end testing


Слишком много

atlekbai · 2025-06-16T13:30:46Z

wheres-my-pizza/README.md

+Build **wheres-my-pizza**, a three-service Go application that tracks a pizza order from placement to delivery.
+All inter-service communication happens through RabbitMQ events—**no synchronous HTTP**.
+A single transactional outbox keeps the DB and broker consistent; consumers stay idempotent via inbox tables.
+The public REST API is **read-only** and lets clients query order status and full event history.
+


Слишком сложно, многие понятие студенту не открыты, твоя цель провести студента по образовательному пути, а не дать пощечину и почувствовать себя глупым

Может в optional добавить? чего много/сложно.

atlekbai · 2025-06-17T13:50:25Z

wheres-my-pizza/README.md

+> you can’t polish your way out of bad architecture
+>


Suggested change

> you can’t polish your way out of bad architecture

>

> You can’t polish your way out of bad architecture.

atlekbai · 2025-06-17T13:53:23Z

wheres-my-pizza/README.md

+
+**Work Queue Pattern**
+- One producer sends tasks to a queue
+- Multiple consumers compete to receive tasks


Suggested change

- Multiple consumers compete to receive tasks

- Multiple consumers wait for the task to arrive, but only one receives it.

atlekbai · 2025-06-17T14:06:25Z

wheres-my-pizza/README.md

Таблицы, сделай как в в техдизайне. Каждый сервис должен иметь свою таблицу

Формат логов

Нарисовать в виде ASCII схему взаимодейсвтия

atlekbai · 2025-06-19T04:02:13Z

wheres-my-pizza/README.md

+## Database Schema
+
+### Orders Table
+


Не хватает описания каждой таблицы, для чего где используется

В таблицах используй простой text, а не varchar

atlekbai · 2025-06-19T04:02:24Z

wheres-my-pizza/README.md

+create table order_status_log (
+    "id"          uuid          primary key default gen_random_uuid(),
+    "created_at"  timestamptz   not null    default now(),
+    order_id      varchar(20)   references orders(id),
+    "status"      varchar(20),
+    "changed_by"  varchar(50),
+    "changed_at"  timestamp     default current_timestamp,
+    "notes"       text


order_id без кавычек

atlekbai · 2025-06-19T04:03:42Z

wheres-my-pizza/README.md

+## RabbitMQ Configuration
+
+### Exchanges and Queues Setup
+
+```
+Exchanges:
+├── orders_direct (type: direct, durable: true)
+│   └── Routing Keys:
+│       ├── kitchen.dine-in
+│       ├── kitchen.takeout
+│       └── kitchen.delivery
+│
+└── notifications_fanout (type: fanout, durable: true)
+    └── Broadcasts to all subscribers
+
+Queues:
+├── kitchen_queue (durable: true, x-max-priority: 10)
+├── kitchen_dine_in_queue (durable: true, x-max-priority: 10)
+├── kitchen_takeout_queue (durable: true, x-max-priority: 10)
+├── kitchen_delivery_queue (durable: true, x-max-priority: 10)
+└── notifications_queue (durable: true, auto-delete: false)
+```


Надо объяснить, даже мне непонятно. Нужно раскрыть в чем отличие fanout от direct

atlekbai · 2025-06-19T04:04:32Z

wheres-my-pizza/README.md

+### Message Formats
+
+**Order Message**
+```json
+{
+  "order_number": "ORD_20241216_001",
+  "customer_name": "John Doe",
+  "customer_type": "vip",
+  "order_type": "delivery",
+  "table_number": null,
+  "delivery_address": "123 Main St, City",
+  "items": [
+    {
+      "name": "Margherita Pizza",
+      "quantity": 1,
+      "price": 15.99
+    }
+  ],
+  "total_amount": 15.99,
+  "priority": 10
+}
+```
+
+**Status Update Message**
+```json
+{
+  "order_number": "ORD_20241216_001",
+  "old_status": "received",
+  "new_status": "cooking",
+  "changed_by": "chef_mario",
+  "timestamp": "2024-12-16T10:32:00Z",
+  "estimated_completion": "2024-12-16T10:42:00Z"
+}
+```


Описать что за message, куда падает, кто читает

atlekbai · 2025-06-19T04:05:48Z

wheres-my-pizza/README.md

+**Required Log Events:**
+- Order received/processed/completed
+- Worker connected/disconnected
+- Status changes
+- Error conditions and recoveries
+- Performance metrics (processing times)


Где какой уровень использовать

atlekbai · 2025-06-19T04:07:10Z

wheres-my-pizza/README.md

+#### Order Processing Flow:
+
+1. Order Service receives HTTP POST request
+2. Validates request data and calculates totals
+3. Stores order in PostgreSQL orders table
+4. Publishes order message to RabbitMQ
+5. Kitchen Worker consumes order from queue
+6. Updates order status to 'cooking' in database
+7. Simulates cooking process (configurable duration)
+8. Updates order status to 'ready' in database
+9. Logs completion and acknowledges message
+
+Outcomes:


Не хватает консистенси: #### Order Processing Flow: и Orders:
Надо использовать хеши

atlekbai · 2025-06-19T04:09:03Z

wheres-my-pizza/README.md

+#### Order Processing Flow:
+
+1. Order Service receives HTTP POST request
+2. Validates request data and calculates totals
+3. Stores order in PostgreSQL orders table
+4. Publishes order message to RabbitMQ
+5. Kitchen Worker consumes order from queue
+6. Updates order status to 'cooking' in database
+7. Simulates cooking process (configurable duration)
+8. Updates order status to 'ready' in database
+9. Logs completion and acknowledges message


Если бы ты делал этот проект, ты бы много уточнял у Аяжан. А как валидировать, как высчитывать. Не хватает деталей

atlekbai · 2025-06-19T04:09:37Z

wheres-my-pizza/README.md

+# Initialize database and queues
+$ ./restaurant-system --setup-db --db="postgres://user:password@localhost/restaurant"
+$ ./restaurant-system --setup-queues --rabbitmq="localhost:5672"


Где он хранит эти конфигурации?

atlekbai

Раздели задачи по фичам, чтобы в каждом задании были описаны элементы только одной части микросервиса: форматы сообщений, запросы, логи, флаги, примеры
Добавь диаграммы, контекст и описание и этого маркдауна

complete_wheres_my_pizza.md

ymoldabe added 4 commits June 16, 2025 02:09

feat: wheres-my-pizza

821b5cd

feat: main

025781f

feat: added wheres-my-pizza project

e719282

fix: support

ffa428a

atlekbai requested changes Jun 16, 2025

View reviewed changes

ymoldabe added 2 commits June 17, 2025 00:28

fix: readme

5600c80

finish

4e1f84b

atlekbai requested changes Jun 17, 2025

View reviewed changes

ymoldabe added 3 commits June 17, 2025 10:40

fix: PR

37a2dd9

fix: PR

d0609d2

fix: Questions.md

a7bdcdb

atlekbai requested changes Jun 19, 2025

View reviewed changes

ymoldabe added 2 commits June 19, 2025 00:35

fix: PR

c1657a6

fix: questions

08a25a2

atlekbai requested changes Jun 23, 2025

View reviewed changes

ymoldabe and others added 9 commits June 27, 2025 15:41

Update Context

75ed9fc

removed: baseline

84dba7e

fix

a6d22ee

update: abstract and questions

e59e139

fix: PR

1aff25c

fix: style

471cdb8

fix: style

70dcdda

fix: PR

babc8a3

fix: PR

220f693

	> you can’t polish your way out of bad architecture
	>
	> You can’t polish your way out of bad architecture.

	- Multiple consumers compete to receive tasks
	- Multiple consumers wait for the task to arrive, but only one receives it.

Conversation

ymoldabe commented Jun 16, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

atlekbai left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants