In my previous article we had concentrated on Design Patterns and UML which
are the most important fundamentals for architecture interviews. One of the other areas which needs to be strong for architects is
an understanding of SOA.
Again I repeat, do not think that you will get an architecture position by reading interview questions. But yes there should be some kind of
a reference which will help you quickly revise what the definitions. Just by reading these answers you get to a position where you are aware of the fundamentals. But if you have not really worked
on these you will surely fail with scenario based questions. So use this as a quick revision rather than
as a shortcut.
To give you a practical understanding I have put all these design patterns in a video format and uploaded on
http://www.questpond.com/FreeDesign1.htm. You can visit http://www.questpond.com
and download the complete architecture interview questions PDF which covers SOA, UML, Design
Patterns, Togaf, OOPs, etc.
Previous parts of the architecture interview questions
You can download the software architecture interview questions PDF here:
Download Software Architecture Interview Questions
UML interview questions, Part 1: SoftArch5.aspx
Happy job hunting......
(B) What is SOA?
SOA stands for service oriented architecture. Before we define SOA let's first define a service. In
the real world, a service is what we pay for and we get the intended service. For instance you go to a
restaurant and order food. Your order first goes to the counter and
then it goes to the kitchen where the food is prepared and finally the waiter serves the food.
Figure: Restaurant and services
So in order to order an item from a restaurant you need three logical departments / services to work together (counter, kitchen, and waiter).
In the same manner in software world, these services are termed as business services. They are self contained and logical. So let’s first define a business service,
SOA definition will be just an extension of that.
Definition of business service: It’s a logical encapsulation of a self contained business functionality.
For instance the figure ‘order system’ shows a simple ordering system which is achieved by different services like payment gateway, stock system, and delivery system coming together. All the services are self contained and logical. They are like black boxes. In short we do not need to understand the internal details of how the business service works. For the external world it’s just a black box which takes messages and serves accordingly. For instance the ‘payment gateway’ business service takes
the message ‘check credit’ and gives out output: does the customer have credit or not. For the ‘order system’ business service ‘payment gateway’ service is a black box.
Figure: Order system
Now let’s revise some bullet points of SOA before we arrive to the definition of SOA.
- SOA components are loosely coupled. When we say loosely coupled
that means every service is self contained and exists alone logically. For instance we take the ‘payment gateway’ service and attach it to a different system.
- SOA services are black boxes. In SOA, services hide there inner complexities. They only interact using messages and send services depending on those messages. By visualizing services as black boxes, services become more loosely coupled.
- SOA service should be self defined: SOA services should be able to define themselves.
- SOA services are maintained in a listing: SOA services are maintained in a central repository. Applications can search the services in the central repository and use them accordingly.
- SOA components can be orchestrated and linked to achieve a particular functionality: SOA services can be used/orchestrated in a plug and play manner.
For instance, the figure ‘Orchestration’ shows two services ‘Security service’ and ‘Order processing service’. You can achieve two types of orchestrations from
it: one you can check the user first and then process the order, or vice-versa. Yes, you guessed right, using SOA we can manage
a workflow between services in a loosely coupled fashion.
So let's define SOA.
SOA is an architecture for building business applications using loosely coupled services which act like black boxes and can be orchestrated to achieve a specific functionality by linking together.
(I) In SOA do we need to build systems from scratch?
No. If you need to integrate or make an existing system as a business service, you just need to create loosely coupled wrappers which will wrap your custom systems and expose the systems functionality in
a generic fashion to the external world.
(I) Can you explain business layers and plumbing layers in SOA?
In SOA we can divide any architecture in two layers. The first which has direct relevance to
the business as it carries out business functions. The second layer is a technical layer which talks about managing computer resources like database, web server, etc. This division is needed to identify a service. Consider the figure ‘Simple order system’. It has various components which interact with each other to complete
the order system functionality.
Figure: Simple order system
The simple order system can be divided in to two layers (see figure 'business and plumbing layer'
- one which is business related and second which is more technical related). You can see the plumbing layer consisting of data access layer, AJAX,
and yes more technical stuff.
Figure: Business layer and plumbing layer
(I) What’s the difference between services and components?
Services are logical grouping of components to achieve a business functionality. Components are implementation approaches to make a service. The components can be in Java, C#, C++ but the services will be exposed in a general format like Web Services.
(A) Can you describe the complete architecture of SOA?
Figure ‘Architecture of SOA’ shows a complete view of an SOA. Please note this architecture diagram is not tied up with implementations of Microsoft, IBM etc. It’s a general architecture. Any vendor who implements SOA needs to fulfill the below SOA components. How
they do it is completely their own technological implementation.
Figure: Architecture of SOA
The main goal of SOA is to connect disparate systems. In order that these disparate systems work they should message each other. ESB (Enterprise
Service Bus) acts like a reliable post office which guarantees the delivery of messages between systems in a loosely coupled manner. ESB is a special layer which delivers messages between applications. In the figure we have shown a huge plump pipe. It’s not hardware or some wire etc. It’s a group of components/software which helps you send and receive messages between the disparate applications. Do not try to code your own ESB, you can think of buying one from Microsoft, IBM, Oracle,
- SOA registry is like a reference database of services. It describes what each service does, where they
are located, and how they can communicate. It’s a central reference of meta-data for services.
- SOA workflow allows us to define a work flow using services in
the SOA registry. We will read more about BPM in further questions.
- Service broker reads the work flow and takes services from the SOA registry and ties them together.
Service brokers are normally middleware like EAI (Enterprise application Integration) products. You can get a list of decent EAI from Sun, Microsoft, and IBM etc.
Process manager is nothing but a collection of SOA registry, SOA workflow, and service broker.
SOA supervisor is a traffic cop ensuring that services do not have issues. It deals mainly with performance issues of the system so that appropriate service levels are met. If any of the services have performance problems it sends messages to the proper infrastructure to fix the issue.
Note: The above explanation is of the general architecture for SOA. Any vendor (Microsoft, IBM, SUN, etc.) who gives
a solution for SOA should have the above components
in some or the other manner. As this is a software architecture book, we will not be covering specific vendor implementations. We would advise the reader to map this
to their vendor products for a better understanding.
(I) Can you explain a practical example in SOA?
(I) What are ends, contract, address, and bindings?
These are the three terminologies on which SOA service stands. Every service must expose one or more ends by which the service can be
made available to the client. The End consists of three important things: where, what,
- Contract (What): Contract is an agreement between two or more parties. It defines the protocol how clients should communicate with your service. Technically, it describes parameters and return values for a method.
- Address (Where): An Address indicates where we can find this service. Address is a URL, which points to the location of the service.
- Binding (How): Bindings determine how this end can be accessed. It determines how communication is done. For instance, you expose your service, which can be accessed using SOAP over HTTP or
binary over TCP. So for each of these communication mediums, two bindings will be created.
Below figure show the three main components of the end. You can see the stock ticker is the service class, which has an end hosted on
www.soa.com with HTTP and TCP binding support and using the Stock Ticker interface type.
Figure: Endpoint Architecture
Note: You can also remember the end point by ABC where A stands for Address, B for bindings, and C for Contract.
(I) Are web-services SOA?
SOA is a thinking, it’s an architectural concept, and web service is one of the technical approaches to complete it. Web services are the preferred standards to achieve SOA.
- In SOA we need services to be loosely coupled. A web service communicates using
the SOAP protocol which is XML based, which is very loosely coupled. It answers the what part of the service.
- SOA services should be able to describe themselves. WSDL describes how we can access the service.
- SOA services are located in a directory. UDDI describes where we can get the web service. This
is nothing but the implementation of the SOA registry.
Other interview questions PDF