Skip to main content

Why we need SOA?

With advent of IT revolution, it is information that people want and technology is a mean to supply it and with time it is provided at lower costs.So keeping the costs continuously low is a challenge.These days business houses have huge dependency on IT and it cannot be wiped out completely.It makes great business sense to save costs that incur on big investments that these organizations do on IT infrastructure for running their complex business processes.


The existing systems in an organization are rarely thrown away and they are valuable asset for enterprise from business point of view.SOA leverages the benefits of integrating new systems with old legacy ones.It is instrumental in linking IT resources and put them to reuse.The cost effectiveness of this style of architecture focuses on services rather on objects.The similar concepts have always been around like Java Connector Architecture propounds the same concepts so SOA is a kind of evolution of existing set of knowledge mainly driven by organizational needs.


The integration of various systems through SOA includes a rich end user experience, application connectivity, all building components forming various business processes work in tandem or a fancy term for that 'orchestration or harmonizing of processes' and one stop shop for all information.This enhances an incremental development and integration approach even existing systems can be split into components with time giving more flexibility for futuristic business requirements.


There is a very common notion of associating SOA with web services but it is beyond that.Web services are a collection of technologies, including XML, SOAP, WSDL, and UDDI, which provide programming solutions for specific messaging and application integration problems. While SOA is an architecture and I think I have written it how it can be exploited by other technologies like CORBA,DCOM,JINI etc.

In telecom systems, for example, there are standalone systems,monolithic in nature which ideally do not collaborate with other systems specially which are network related as network management system is.SOA suits a great deal to such situations where interoperability opens new vistas.


While designing developing and implementing those services a user needs not be worried about its details and therefore they can run on distributed environments across networks.This also maximizes their reuse.

Comments

Popular posts from this blog

Asynchronous Vs. Synchronous Communications

Synchronous (One thread):   1 thread -> |<---A---->||<----B---------->||<------C----->| Synchronous (multi-threaded):   thread A -> |<---A---->| \ thread B ------------> ->|<----B---------->| \ thread C ----------------------------------> ->|<------C----->|

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag...

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol