Scalable and reliable SOA messaging framework
Software that is tightly coupled poses great challenges to software engineers and managers when it comes to modification. This is especially so if client’s demands are ever changing. Good software engineers will invest more effort to ensure software maintainability. However, significant amount of ti...
Saved in:
Main Author: | |
---|---|
Other Authors: | |
Format: | Final Year Project |
Language: | English |
Published: |
2013
|
Subjects: | |
Online Access: | http://hdl.handle.net/10356/55034 |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Institution: | Nanyang Technological University |
Language: | English |
Summary: | Software that is tightly coupled poses great challenges to software engineers and managers when it comes to modification. This is especially so if client’s demands are ever changing. Good software engineers will invest more effort to ensure software maintainability. However, significant amount of time may be required for coming up with good software design. Even with good designs there is also a limit to the changes that can be made.
This project aims to build a service oriented architecture (SOA) framework which leverage on Extensible Messaging and Presence Protocol (XMPP) and Java Message Service (JMS) messaging technologies. SOA eliminate the problem of tightly coupled systems by viewing software pieces as services. These services can exchange data with different programs with minor or no modification, hence they are highly reusable which result in lower maintenance cost.
As part of SOA requirements, services are designed as independent units which provide functionality to consumer. Services are built on JMS which provides loose coupling for the different services. JMS helper class is developed to facilitate future service developers. Consumers of services are client software built on XMPP which provides service discovery, service request and authentication and authorization.
JMS and XMPP are two different technologies, in order to communicate, a middleware is required. Middleware, XMPP-JMS Bridge is designed to be reliable and easily scalable so as to handle the varying number of services.
SOA built in this project provides service developers the flexibility of modifying the services and each XMPP Client can benefit from accessing multiple services through a secured network. |
---|