Carlo (Name changed) was looking for more elaborated explanation on SOA and how Informatica power center 9 ( Informatica 9 .1 Architecture ) is SOA based. To understand this we are going to see this in two parts. (1) Evolution of architectural blue prints over the time. (2) How Informatica power center version 9 is SOA based.
Who Should read this Post: This post will not be useful for those who work in Designs patterns and reusable components. Objective of this post is to cover SOA implementation in Informatica power center. We will cover it as necessary and in our scope to understand Informatica product following SOA blueprint. It has Very basic description of SOA history (architectural blueprint/Design Patterns).
How architectural Blueprints Has Evolved Over The Period Of Time
Stand alone system or architecture: initial days of computing we used have stand alone system to process the data and application used to reside on them. To process that data someone has to save the data in that standalone system and then application residing on it used to process the data and processed data could be retrieved from the system later in paper or floppy disk or in any other ways you need.
Two tier architecture: After LAN network introduced it has evolved application data processing capability as well. Now computers were networked through LAN. In other words computers can share the data across. This made a requirement to have two-tier application architecture. Your application core logic used to be on server and other computers used to have application client installed. Application client used to communicate to send data and after get it processed they were able to retrieve the data. Example – code written in visual basic, Delphi etc
Three tier architecture: network has evolved and internet has established for general usage. Internet has created a need of another architecture which can server distributed application needs accessed across the globe. All internet based enterprise applications are based on three tier application blueprint. Main component of this blueprint were server, application logic, browser based client application. Application logic is hidden and located at server, client send the request to process the data, Server picks the application logic and process the data and sends back to client. This is a brief overview of web based applications and their working pattern.
EAI: enterprise application integration is also one mehtodology which we need to consider before we get in to SOA. An organization IT needs gets served by many applications. When there was a need to get the data all of them to do analytics EAI has came in to the picture. EAI is usually known as application integration method through which two applications can share the data to each other. Kindly read Enterprise application integration post for more understanding.
Mainly whatever purpose EAI caters to SOA also built to do the same. Though, SOA is not an enhancement of EAI. It is entirely different from EAI.
Why do we need SOA ? Over the period of time as networked evolved and application needs also evolved. There was a need to process high amount (larger volume) of data. Three-tier architecture was good but not sufficient enough to cater this need. So bigger needs of EAI something needed which can take care of next generation enterprise systems which is very fast indeed.
Basic Definition of SOA: SOA is not a technology or language. SOA is architectural blue print, design pattern or design approach for application development. Very basic and main objective of SOA is speed in other words agility. Any application or tools developed with SOA guidelines have higher agility.
We will not get into more details here which is necessary for Architect who design SOA based tools or applications. For that we need to look into web services, DCOM, CORBA, Websphere, Java, .net etc
SOA in General: In SOA we create services and it can be web services, data services, integration services etc. they are called as middleware. Middleware carries the data. Each middleware has different processing capabilities. Read to understand type of middleware . Some of Informatica middleware are known as data services.
How Informatica 9.1 Architecture Follows SOA Design?
If you see in Informatica 9.1 architecture we have lot of management components and other services. These services make informatica to follow SOA. In SOA they are explicitly called as data services. Whenever a request happens, these data service interacts with Database or Server component to get the desired result. It makes Informatica 9 more agile and scalable (capability to handle large amount of data). Apart from this SOA architecture helps power center to integrate new adapters and plug-in easily to expand it capability to process any type of data. With SOA user gets seamless integration.
I hope this post will cover below from above description.
- What is SOA? Define SOA, is it a tool or framework?
- Why Informatica 9.1 architecture is SOA based?
- What is the difference between Informatica 9.1 architecture and previous one?
- What are added components in new Informatica 9.1 architecture ?
- What are the advantages of SOA blueprint?
- Explain evolution of architectural blueprints?
- Explain SOA from different perspective or people having different role?
Soon I will update one Easy Informatica 9.1 Architecture pic. Please let me know if something else can be added here? 🙂