Hi Elena,
The application components in service-oriented architecture (SOA) 'may' be centralized, distributed, or a mixture of both. Depending on the complexity, and number of underlying services used by the SOA.
It looks like you're trying to understand the difference between a centralized SOA vs. distributed SOA. In most cases, SOA will be a hybrid of centralized AND distributed services.
Without getting too complicated, let's send a request to a distributed service. To let's say, to get a boolean value. When you can directly poll each logically separated application and get the same result, it's distributed. At least the front-end is distributed.
north.soa.application.domain.tld = TRUE
south.aos.application.domain.tld = TRUE
east.soa.application.domain.tld = TRUE
west.soa.application.domain.tld = TRUE
These SOA applications 'could' use a centralized data source, or the data source 'could' be distributed. If the data source was distributed and you add a security layer that's centralized, you end up with a SOA that's a hybrid.
Hope this helps!
------------------------------
Brian LaVallee
INVITE Communications Co. Ltd
------------------------------
Original Message:
Sent: Mar 29, 2018 00:00
From: Elena Kretova
Subject: Centralized/Distributed/Service oriented Architecture/Application
I am doing a system architecture and my knowledge from college doesn't help me when it comes to understand the subtle differences between centralized, distributed and service oriented architecture/application.
If I take a typical client/server architecture, the client sends requests to a server, the server then sends responses to the client. That is a centralized architecture.
An application that handles both oracle soa server and client sides will be a distributed application(because working on different platforms), but that is still a centralized architecture.
Therefore, a distributed architecture must involve a distributed application.
------------------------------
Elena Kretova
Tekslate
------------------------------