InfoQ Homepage Messaging Content on InfoQ
-
Database-based High Performance Message Exchange Service for Enterprise Applications
Database Message Exchange Service (DBMES) stores messages in database for a Windows service to deliver to external services and vice versa. A message can be anything – an order, some task, a message for a destination message queue, a payload for calling external webservice and so on. DBMES decouples the client from the external services that are not on the same network or not always available.
-
Interview and Book Excerpt: ActiveMQ in Action
In this article, InfoQ spoke with Bruce Snyder, co-author of ActiveMQ in Action book, about the main motivation for writing the book, transaction management and messaging security aspects in ActiveMQ container and emerging trends in the messaging space.
-
An Introduction to SpringSource's Advanced Message Queuing Protocol Support
This article looks at the problems AMQP is aiming to address, exploring some of the debate and controversy that the draft specification has generated. We talk to SpringSource's Mark Pollack and Mark Fisher, to find out more about their AMQP-based products, and iMatix's Pieter Hintjens about his work on the specification and his concerns around the direction it has taken.
-
How to Extend the Axis2 Framework to Support JVM Based Scripting Languages
Heshan Suriyaarachchi covers some of the key concepts of the Apache Axis2 Web Service engine and how it can be extended to support JVM based scripting languages such as Jython, Jruby, etc allowing them to be used to both expose web services and write web service clients.
-
Nobody Needs Reliable Messaging
Marc de Graauw challenges the notion that transport-level reliability mechanisms like WS-ReliableMessaging are needed, showing how business-specific logic for in-order and exactly-once processing do the job much better with examples from Dutch Healthcare's SOA.
-
REST and SOAP: When Should I Use Each (or Both)?
Web developers today have a myriad of technologies they can choose from; for example, the two approaches for interfacing to the web with web services, namely SOAP and REST. Both approaches work, both have advantages and disadvantages to interfacing to web services, but it is up to the web developer to make the decision of which approach may be best for each particular case.
-
mySOA: Agile, Governed and Sustainable
William El Kaim, Lead Architect at Carlson Wagonlit, provides a rare glimpse at all the choices, and the rationale behind them, he and his colleagues have made while building their organization's Service Oriented Architecture. How does your SOA compare? What will be the major evolutions in the next few years? How will the Cloud impact current SOAs?
-
Resource-Oriented Architecture: The Rest of REST
In this first article in the Resource-Oriented Architecture series, Brian Sletten discusses the REST architecture style, the history of SOA, SOAP and WS-*, the Semantic Web, URLs as identifiers, URIs and URNs, freedom of form, logically-connected late-binding systems, HATEOAS, and the impact of the Semantic Web upon software systems.
-
A Decade of SOA: Where are we, Where are we Going?
SOA is 10 years old. InfoQ has gathered Jeff Andres, Eric Ballou, Dave Hollander and William El Kaim, all Enterprise Architects with a long experience in SOA, to share their perspectives on where we are and where we are heading, as part of a virtual panel. They talk about Reuse, Business/IT alignment, Governance,...
-
Interview and Book Excerpt: Mark Richards' Java Message Service 2nd Edition
Java Message Service, 2nd Edition, by Mark Richards, covers JMS topics such as the two programming models, publish-and-subscribe and point-to-point, Messaging Filtering and Transactions. InfoQ spoke with Mark about his new book. Topics covered in the interview include EJB 3.0, Spring Message Driven POJO's (MDP)and Enterprise Service Bus (ESB) architecture.
-
Getting started with AMQP and RabbitMQ
Joern Barthel introduces the Advanced Message Queuing Protocol (AMQP), and illustrates it's useage with Ruby-based client and an EDA-style app. The open source RabbitMQ server is used on the backend (which is written in Erlang).
-
Routing Messages in Mule
Jackie Wheeler discusses the use of Mule as a message routing solution for SOA middleware. The article covers key concepts, selection of a message style; passing, filtering and splitting messages; and, calling external services. Examples of messaging implementation are included.