2. SOA
SOA is an architectural style to promote enterprise business functions as services
●
Provides enterprise patterns for systems development and integration
●
Supposed to reduce costs and increase agility
●
Idea behind using SOA is to build new services using existing services
3. Service in SOA
●
Service in SOA can be defined as a self-contained, independently developed
and maintained reusable software component supporting specific business
functions
●
Service is not a programming construct or a set of APIs, but is rather an
architectural artifact
●
Unit of design, implementation, and maintenance used for implementation of
enterprise solutions
4. Web Service
●
Web services are a new breed of Web applications
●
A Better RPC and Distributed Component Model
●
Reusable software components
●
Platform independent application integration using SOAP over HTTP
●
Perform better when compared with RMI/IIOP, CORBA or DCOM
6. SOA & Web Apps
Looking from the software engineering perspective
●
SOA increases reusability and agility
●
Reduce cost of development in the long run
7. SOA & Web Apps
Looking from the operational perspective
8. SOA & Web Apps
Problems using SOA in Web Applications
●
Latency issues
●
Single point of failure
●
Tightly coupled
●
Maintaining Throughput
●
SLA Dependencies
17. SOA & Web Apps
Problems using SOA in Web Applications
●
Latency issues
●
Single point of failure
●
Tightly coupled
●
Maintaining Throughput
●
SLA Dependencies
18. SOA & Web Apps
The single point of failure can addressed by using ESB (Enterprise Service Bus)
the latency issue a difficult problem to solve.
Using SOA + Event-Driven Architecture will alleviate the problems caused by
SOA.
Look at my EDA Presentation on Slideshare.net
“Lie Cheat Steal to build Hyper-Fast Applications using Event-Driven Architecture”