What are possible variations of a service-oriented architecture? Can you share any practical example of a service-oriented architecture in your experience? Will be great if you can share a link or diagram that explains the architecture? I intend to create a comparison of SOAs and present proposals for improvement in the way it works.
Thanks
Try to think in Role Orientation , instead Service orientation , because Role is entitle to do services , check Agent Role Locking Theory ARL.
It sounds interesting - but what happens when the agents need to work together to provide a service. Does't it look like segregation of perspectives only? What is the real advantage you think ARL based systems have over SOA especially when it comes to dynamic and real-time systems?
You should start with the OASIS document defining the SOA Reference Architecture. It defines the essential patterns and is the basis for other reference architecture, including that of the Open Group
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra.html
AS to the question of combining / substitution components of a service on different machines, make sure you understand the Service Component Architecture (SCA), also defined w/i OASIS and used by many corporations
http://www.oasis-opencsa.org/sca
Hi Nauman,
SOA is an architectural style for building business applications by means of services. Application comprises collection of services which communicate through messages.
Some Important SOA Characteristics
- Services should be independent of other services and each service is self-contained.
- Services should be published into a location (directory) where anyone can search for it.
- Services should be able to communicate with each other asynchronously.
- Services should be able to define themselves.
- When we talk about a RegisterCusomer service it means, service will do all the necessary work for us, we are not required to care about anything.
- Services should be able to answer a question what is does
- Services should support reliable messaging.
- Services should support secure communication.
For example, if you want to develop a web application (ASP.NET, JSP, PHP no matters) in SOA architecture, you will need basically four types of servers:
- Web Servers: Needed for only rendering HTML pages.
- ESB (Enterprise service bus) Servers: Routes client requests to BackEnd servers. Manages messaging.
- BackEnd Servers: Services and their functions are hosted here.
- Database Servers: Relational or NoSQL DB
- Badges
- Science topic
- Similar topics
- Human-Computer Interaction
- Collaboration