From the vice president and chief technologist for SOA at Oracle Corporation

Dave Chappell

Subscribe to Dave Chappell: eMailAlertsEmail Alerts
Get Dave Chappell: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Dave Chappell

Today is the day we officially launch Oracle Fusion Middleware 11g. Fusion Middleware 11gR1 is the result of a herculean effort that is 3+ years in the making. The major areas of investment have been: The completion of the integration between Oracle and BEA products into unified suites.  This matches to the month the schedule that we had committed to publicly when announcing the BEA Strategy last June.  This continues our excellent track record of buying best-of-breed software and integrating it together into a common environment. Improving the efficiency of modern data centers by extending the capabilities of Application Grids.  We now take advantage of new hardware and software advancements such as multi-core processors, 64-bit addressable memory, RAM-based storage, 10GB Ethernet systems, and virtualization to allow large sets of compute capacity and memory to be... (more)

Benchmarking JMS-Based E-Business Messaging Providers

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

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)

Beyond The JMS Specification

The Java Message Service (JMS) is a specification put forth by Sun to define a common set of APIs and common semantics for messaging-oriented middleware providers. An increasing number of MOM vendors have embraced this specification, and new vendors are building messaging products suitable for doing business-to-business communication across the Internet. The result is a landscape where developers can feel comfortable about writing an application using a standard set of APIs while still having an ample selection of JMS-compliant vendors to choose from. However, the JMS specificat... (more)

Distributed Logging Using The JMS

Every software system has logging requirements so application processing can be monitored and tracked. Modern distributed systems, which are usually based on application frameworks, require a logging solution that can cope with multiple processes on multiple hosts sending logging information to a single logging service. Many application frameworks widely used today, whether they're high-level frameworks like J2EE application servers or low-level frameworks like CORBA ORBs, don't provide a distributed logging facility for application code. Using JMS queues to log application mess... (more)