The Java Message Service (JMS) is an enterprise-capable middleware component
based on message-oriented middleware (MOM) fundamentals. Since its
introduction as a Java software specification in November 1998, vendor
implementations have brought JMS forward as a first class, e-business
messaging communications platform suitable for exchanging critical business
data over the Internet.
This article is the first in a series of three that explain the application
program interfaces (APIs), the message delivery semantics, and the deployment
environments that are well suited to JMS applications.
What Is JMS and Where Did It Come From?
JMS defines the first and only standard for asynchronous MOM implementations.
The specification defines a common set of APIs and message delivery
semantics. A developer can write an application using the JMS APIs and enjoy
the freedom of choosi... (more)
The notion of guaranteed delivery of Java Message Service messages has been
lightly touched on in other recently published articles on JMS. But what
really makes a JMS message "guaranteed"? Should you just take it on faith, or
would you like to know what's behind it?
This article answers these questions via a detailed discussion of message
persistence, internal acknowledgment rules, and message redelivery. Using
excerpts condensed from the book we coauthored, Java Message Service, we'll
explain how JMS guaranteed messaging works - including once-and-only-once
delivery semantics,... (more)
Since releasing my latest book, Enterprise Service Bus (O'Reilly Media,
2004), I have been doing a fair amount of visiting corporations, conducting
seminars, and generally discussing with enterprise architects the subject of
enterprise service-oriented architecture (SOA) and how an enterprise service
bus (ESB) backbone can be leveraged to provide a framework for an enterprise
SOA. Along the way, I have been asked many questions about the nature of an
ESB. I have also fended off some misconceptions that have been growing in the
general IT population regarding what an ESB is and wh... (more)
The Open Services Gateway Initiative (OSGi) Alliance is working to realize
the vision of a "universal middleware" that will address issues such as
application packaging, versioning, deployment, publication, and discovery.
In this article we'll examine the need for the kind of container model
provided by the OSGi, outline the capabilities it would provide, and discuss
its relationship to complementary technologies such as SOA, SCA, and Spring.
Enterprise software is often composed of large amounts of complex
interdependent logic that makes it hard to adapt readily to changes in
David Chappell's Blog
Across financial services firms we have been seeing a new set of business
priorities. There are the "grow the business" priorities that are primarily
centered around things like improving customer intimacy and increasing
competitive differentiation. here are also ongoing issues of compliance to
regulation and risk mitigation while also keeping an eye towards improving
cost efficiency. The thing that hasn't changed is that IT is viewed as the
enabler to overcome these challenges.
Financial institutions are pushing the envelope and require more processing... (more)