- Message-driven processing is an approach used within the client/server computing model in which a client (for example, your Web browser) sends a service request in the form of a specially-formatted message to a program that acts as a request broker, handling messages from many clients intended for many different server applications. A message may contain the name of the service (application) wanted and possibly a requested priority or time of forwarding. The request broker manages a queue of requests (and possibly replies) and screens the details of different kinds of clients and servers from each other. Both client and server need only understand the messaging interface. Message-driven processing is often used in distributed computing in a geographically-dispersed network and as a way to screen new client applications from having to interact directly with legacy server applications. Special software that provides message-driven processing is known as middleware.
In IBM's MQSeries middleware messaging product, its MDp (for "message-driven processor") provides an example. MDp is an intermediary layer between clients and a legacy system of applications, and serves as a request broker between clients and applications. The client formulates a request; MDp (which retains information about which applications and databases are to be invoked and where they reside) then breaks the request down into work units and sends these out to the appropriate server applications and databases. After executing the tasks, the back-end processes return the results to MDp, which in turn formulates replies to return to either the requesting client or some other target destination.
 |
Learn more about Web services development |
| Operating system virtualization and Web services: Web services development and operating systems virtualization may be two different types of abstraction, but virtualization techniques look like they can have positive impact. |
| Creating rich Web service clients with Flash and Flex: Flash and Flex, titans within the RIA universe, now have XML, Ajax and scripting language functionality that make them better suited for Web services development. |
| Oracle links SOA, data services, BI and BAM: When it comes to incorporating data services, business intelligence (BI), and business activity monitoring (BAM), Oracle has not lost sight of its database roots. |
| Is Ruby on Rails ready for enterprise SOA?: Ruby on Rails promises ease in RESTful SOA development, but for it to move up to enterprise class, developers need to know how to make it scalable. |
| 2006 JavaOne coverage: A compilation of stories written about the JavaOne conference held in San Francisco this past May. |
| Chapter of the week: Security and Ajax: This chapter, excerpted from Ajax in Action, discusses security-related concerns that have particular implications for Ajax. |
| Chapter of the week: XML Web services: This chapter, excerpted from Core C# and .NET, takes a look at the pluses and minues of implementing and consuming Web services in a .NET environment. |
| Chapter of the week: Working with Beehive Web services and JSR 181: This chapter, excerpted from Pro Apache Beehive, explores the Web service capabilities that are a part of Apache Beehive. You'll learn about JSR 181, Web Services Metadata for the Java ... |
| Chapter of the week: Introduction to Web services technologies: This chapter, excerpted from Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services, focuses on the standards that make up the Web services platform and how Web ... |
| CONTRIBUTORS: |
Jonathan Caforio |
| LAST UPDATED: |
16 Dec 2002
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|

 |
More resources from around the web:
|


');
// -->



|