SOA - Interview Questions
What is SOA?
SOA is Architecture Principle for building the reusable/loosely coupled and interoperable services which maps to business functionalities and business requirements in Enterprise level.
What are the Benefits in EA Level ?
Benefits categorized into two
1) Business
SOA helps greater alignment between Business and IT while generating more flexibility , it will helps in Business ie business can change the process dynamically and faster .
It helps to easy integration with Partners/customer's services into Enterprise level , it will generate the Reveniew and reduced the cost.
SOA is not necessary to start from scratch instead we reuse the existing asset to wrap/expose into services . It will reduced the cost
2) Technical
SOA helps to standardize the Interface contract and guidelines
Loosely coupled principle used to hide the implementation from consumers . We can change the implementation with /with out min changes in consumer side . Some scenario we need to implement the changes with out backward compatibility, in such case we can introduce versioning to achieve the backward compatibility .
Reusability to address the duplicate issue in enterprise level.
Developer only focused on the business logic rather than focused on cross cutting concern in services level
SOA build with ESB which will provide integration capability like transformation/transportation /mediation and etc.
3) What are basic Principle of SOA
Loosely Coupled
Reusability
Standardize the Interface contract
Composition of Services
Service stateless
Service Abstraction
4) How do we migrate into SOA?
Reusability :
It helps to identify the Duplicate Services in Enterprise level and reuse the existing assets as much as possible. If the existing the system does not have service capability then we will wrap the Service interface for those legacy application
Loosely Coupled:
It helps to hide the implementation of services from consumers and also provides the infra to consume the services through middleware rather than consume directly
Standardize IC:
We need to standardize the IC along with Data model for all the services .
Service Composition
It will helps to aggregate the services and construct the single response to the consumer
6) Common Pitfalls in SOA
Setting up the infrastructure , Developer more focus on SOA Solution rather than business problem
Guides to solve the multiple problem at once instead of small piece of problem
We need to compromise the performance since it will take more latency .
Spend more money in upfront with lower revenue
7) Top down and Bottom up approach , which approach suits for SOA World ?
Top down -
Starts with IC and follows the implementation .
Mostly very good approach for new services or service implementation starts from scratch
Bottom up approach
generating the IC from implementation .
In SOA world , prefer the Top down approach but some scenario we need follow the bottom up . so ideal case it will mix of both approach
8) When SOA is not suits?
Homogeneous IT Environment
Performance is Critical factor
There is no more frequent changes in the application
Faster delivery application ie agile model delivery with independent service /infra
Small scaled Company is not ready spend money in SOA
9) What is difference between SOA and WS?
SOA is Architecture element and WS is one of the way implementing the services in SOA context or WS is technical approach to implement the services in SOA .
10) What is service orchestration and Chorography ?
SOA is Architecture Principle for building the reusable/loosely coupled and interoperable services which maps to business functionalities and business requirements in Enterprise level.
What are the Benefits in EA Level ?
Benefits categorized into two
1) Business
SOA helps greater alignment between Business and IT while generating more flexibility , it will helps in Business ie business can change the process dynamically and faster .
It helps to easy integration with Partners/customer's services into Enterprise level , it will generate the Reveniew and reduced the cost.
SOA is not necessary to start from scratch instead we reuse the existing asset to wrap/expose into services . It will reduced the cost
2) Technical
SOA helps to standardize the Interface contract and guidelines
Loosely coupled principle used to hide the implementation from consumers . We can change the implementation with /with out min changes in consumer side . Some scenario we need to implement the changes with out backward compatibility, in such case we can introduce versioning to achieve the backward compatibility .
Reusability to address the duplicate issue in enterprise level.
Developer only focused on the business logic rather than focused on cross cutting concern in services level
SOA build with ESB which will provide integration capability like transformation/transportation /mediation and etc.
3) What are basic Principle of SOA
Loosely Coupled
Reusability
Standardize the Interface contract
Composition of Services
Service stateless
Service Abstraction
4) How do we migrate into SOA?
Reusability :
It helps to identify the Duplicate Services in Enterprise level and reuse the existing assets as much as possible. If the existing the system does not have service capability then we will wrap the Service interface for those legacy application
Loosely Coupled:
It helps to hide the implementation of services from consumers and also provides the infra to consume the services through middleware rather than consume directly
Standardize IC:
We need to standardize the IC along with Data model for all the services .
Service Composition
It will helps to aggregate the services and construct the single response to the consumer
6) Common Pitfalls in SOA
Setting up the infrastructure , Developer more focus on SOA Solution rather than business problem
Guides to solve the multiple problem at once instead of small piece of problem
We need to compromise the performance since it will take more latency .
Spend more money in upfront with lower revenue
7) Top down and Bottom up approach , which approach suits for SOA World ?
Top down -
Starts with IC and follows the implementation .
Mostly very good approach for new services or service implementation starts from scratch
Bottom up approach
generating the IC from implementation .
In SOA world , prefer the Top down approach but some scenario we need follow the bottom up . so ideal case it will mix of both approach
8) When SOA is not suits?
Homogeneous IT Environment
Performance is Critical factor
There is no more frequent changes in the application
Faster delivery application ie agile model delivery with independent service /infra
Small scaled Company is not ready spend money in SOA
9) What is difference between SOA and WS?
SOA is Architecture element and WS is one of the way implementing the services in SOA context or WS is technical approach to implement the services in SOA .
10) What is service orchestration and Chorography ?
Comments
Post a Comment