Web Services are becoming the chosen way of exposing interoperable units of work as services. Today consumers and providers of software services talk different languages, and SOAP makes them understand each other. SOAP can be transported via almost anything, and we sometimes joke that we can even do SOAP over FedEx if necessary.
Some architects lay down their design based on SOAP over HTTP services, but as the project grows, they face challenging scalability problems. One of the most accepted ways of addressing these problems is to use JMS. We usually provide HTTP wrappers - still exposing our services as SOAP over HTTP, but those are lightweight fronts that just send or publish a message to a queue or a topic to trigger heavy business logic.
About Stanimir Stanev Stanimir Stanev is a senior consultant at MomentumSI's Enterprise Architecture Solutions practice. He has many years of experience focusing on providing enterprise architecture and strategy expertise to companies looking to migrate to or maximize the advantages of SOA principles.
About Rob Bartlett Rob Bartlett is a senior consultant at MomentumSI's Software Development Solutions practice. He has over a decade of experience in technical roles, guiding major corporations in the design, implementation, and integration of business solutions.
Reader Feedback: Page 1 of 1
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
Click to Add our RSS Feeds to the Service of Your Choice:
.gif)
Some architects lay down their design based on SOAP over HTTP services, but as the project grows, they face challenging scalability problems. One of the most accepted ways of addressing these problems is to use JMS. We usually provide HTTP wrappers - still exposing our services as SOAP over HTTP, but those are lightweight fronts that just send or publish a message to a queue or a topic to trigger heavy business logic.
