Per-operation services and IAM for a small business

Golden Bite is a premium treats and catering business in Abuja, served by three surfaces: a customer storefront, an operations dashboard, and a staff mobile app. The interesting decision is that a small business runs on an isolation model usually reserved for much bigger systems.

Per-operation, not one god-service

Rather than a single backend that can do everything, Golden Bite leans on a per-operation database/service and IAM discipline (the pattern I nickname the "Golden Bite arch"). Each capability gets its own narrow slice of authority, so a bug or a compromise in one operation has a small blast radius instead of the run of the whole system.

The supporting cast

• Zod validates at the edges, so bad input dies early.
• SWR + axios handle data fetching on the client.
• ioredis caches the hot reads.
• Prometheus makes each operation independently observable — you can watch a single capability's health instead of guessing from an aggregate.

Why bother at this size

Because the discipline is free once it's a habit, and it scales down as gracefully as it scales up. The same instinct — isolate operations, give each the least authority it needs, measure them separately — is what shows up, much larger, in the platforms. Practising it on a bakery keeps it sharp.