Tomcat constraint - workarounds/options?
Messaging and AWS services aren’t necessary saying “no” to Tomcat.
I was thinking:
- Apache Camel running as a plain-old Java application. Though I’ve always relied on Wildfly/Fuse add-on, I think you can run this as its own application.
- Amazon (AWS) hosting your messaging and light-weight processing needs via Lambda.
- ESB - Though this is pushing the constraint given that some ESB services are, or were, just specialized application containers.
When I build event-based, messaging systems… I typically bridge the inbound/outbound messages between local JMS implementations (ActiveMQ, Rabbit, etc) and enterprise/cloud-base sysetms (AWS, MQ, etc). Using a sort-of “store-and-forward” architecture. Provides local horizontal robustness and availability while keeping hooked into external communication channels.