Learn about some of the application architectural issues in applications that use messaging and JMS in general. This article examines state vs application decoupling in JMS applications, looks at synchronous vs asynchronous use cases, examines some architectural anti-patterns, and discusses the consequences of certain JMS topologies with respect to transactional requirements. It also recommends some better architectures and solutions.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
About the Author
Roland Barcia is a Consulting IT Specialist with IBM's Software Services for WebSphere organization in the software division, working as a WebSphere Studio Application Developer and WebSphere Application Server Consultant. He has helped several clients implement WebSphere, J2EE, and Web Services solutions as an architect and a mentor. Roland has published articles in WebSphere Technical Journal and WebSphere Developer Domain and has worked in the Application Integration space for over 6 years. He is also the lead author of the up and coming book titled, IBM WebSphere: Enterprise Deployment and Administration. Roland has Bachelor Degrees of Science in Mathematics and Computer Science from Saint Peter's College and is currently pursuing a Masters of Science in Computer Science at the New Jersey Institute of Technology.