The past several years have seen some significant technology trends, such as
service-oriented architecture (SOA), enterprise application integration
(EAI), business-to-business (B2B), and Web services. These technologies have
attempted to address the challenges of improving the results and increasing
the value of integrated business processes, and have garnered the widespread
attention of IT leaders, vendors, and industry analysts. The enterprise
service bus (ESB) draws the best traits from these and other technology
trends to form a new architecture for integration. The ESB concept is a new
approach to integration that can provide the underpinnings for a loosely
coupled integration network that can scale beyond the limits of a
hub-and-spoke EAI broker.
An ESB is a highly distributed, event-driven, enterprise SOA that is geared
toward integration. It is a standards... (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
r... (more)
Benchmarking any distributed computing middleware product is a complex task.
Knowing how well a distributed infrastructure will perform under heavy load
with a large number of concurrently connected users is a key factor in
planning a development and deployment strategy.
With the advent of Java Message Service (JMS) as the standard for a global
class middleware infrastructure, development organizations can enjoy the
luxury of building distributed applications using a common set of APIs and
message delivery semantics. At the same time they can pick and choose from a
variety of JM... (more)
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 appli... (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)