Skip to main content

An Introduction to Middleware Architectures and Technologies

  • Chapter
  • First Online:
Essential Software Architecture

Abstract

I’m not really a great enthusiast for drawing strong analogies between the role of a software architect and that of a traditional building architect. There are similarities, but also lots of profound differences. But let’s ignore those differences for a second, in order to illustrate the role of middleware in software architecture.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 79.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    The following paper discusses of issues: J. Baragry and K. Reed. Why We Need a Different View of Software Architecture. The Working IEEE/IFIP Conference on Software Architecture (WICSA), Amsterdam, The Netherlands, 2001.

  2. 2.

    Common Object Request Broker Architecture.

  3. 3.

    MOM can also be simply implemented in a point-to-point fashion without a centralized message queue server. In this style of implementation, ‘send’ and ‘receive’ queues are maintained on the communicating systems themselves.

  4. 4.

    An application that needs to receive messages in the order they are sent is not suitable for operating in this a clustering mode.

  5. 5.

    And the wide area network doesn’t support multicast.

  6. 6.

    The platform was known as Java 2 Platform, Enterprise Edition or J2EE until the name was changed to Java EE in version 5.

  7. 7.

    http://java.sun.com/javaee/reference/faq/persistence.jsp

  8. 8.

    See http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller

  9. 9.

    Specifically, the annotation contains a mappedName element that specifies the JNDI name of the JMS queue where messages are received from.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Ian Gorton .

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Gorton, I. (2011). An Introduction to Middleware Architectures and Technologies. In: Essential Software Architecture. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-19176-3_4

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-19176-3_4

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-19175-6

  • Online ISBN: 978-3-642-19176-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics