Question

A logistics company is migrating an on-premises order-processing system to AWS. The monolith currently writes shipment events to a self-managed IBM MQ broker, and several downstream batch jobs poll the queue on fixed schedules. During peak season the polling jobs fall behind, and adding new consumers requires code changes and broker reconfiguration. Leadership wants to modernize during the migration to eliminate broker administration, allow new consumers to be added without touching producers, and scale automatically with load while minimizing operational cost. Which target architecture best meets these requirements?

Accepted Answer

Publish shipment events to an Amazon EventBridge event bus and let each downstream consumer subscribe with its own rule and target, adding new consumers by creating additional rules.

Answer

Rehost the IBM MQ broker on Amazon MQ (ActiveMQ engine) and keep the downstream jobs polling on their existing schedules.

Answer

Send shipment events to a single Amazon SQS standard queue and have all downstream jobs share the queue, scaling by increasing the number of pollers.

Answer

Deploy Amazon MSK and have producers write to a Kafka topic while consumers use consumer groups to read events at their own pace.