Poja Uses Naming Conventions to Auto-Wire AWS Infrastructure for Spring Boot Apps

Spring Boot developers already rely on conventions like package placement and classpath scanning to wire application internals, but AWS infrastructure — queues, retries, permissions, and routing — typically still requires manual configuration. This gap means a simple requirement like async processing translates into a complex set of infrastructure decisions that developers must declare separately from their application code. Poja, a framework built on top of Spring Boot, extends the convention-over-configuration principle to cloud infrastructure by inferring SQS queues, dead-letter queues, and visibility timeouts from just two developer-defined values in the event class. Developers need only extend a base event class, name the consumer service after the event, and place both in expected packages — Poja resolves the wiring through string concatenation and calculated timeouts. The approach aims to eliminate the split between application logic and infrastructure declaration by treating AWS resource configuration as a derivable convention rather than an explicit task.