APIGateway
A single entry point that routes, authenticates, and rate-limits requests to backend services.
Why we need this / what value this brings
A single entry point centralizes cross-cutting concerns (auth, rate limiting, routing) instead of duplicating them per service.
When to use this
Once there's more than one backend service that needs consistent auth/rate-limiting applied at the edge — not needed with a single backend.
How to use or implement this
Not yet relevant with Localz's single FastAPI backend; revisit if/when it splits into multiple services.
Research questions
- Does Localz need one yet with a single backend, or only once it's multiple services?
Empty folder — drop notes, links, and findings here as you research.