Term
|
Definition
It is a architecture for building business applications using loosely coupled services (which act like black boxes) and can be combined to achieve a specific functionality. |
|
|
Term
What are some important points of SOA?
(Hint: 5) |
|
Definition
- Components are loosely coupled.
- Services are black boxes.
- Services are self-defined.
- Services are maintained in a listing.
- Components can combine to achieve a particular functionality. |
|
|
Term
In SOA, do we need to build systems from scratch? |
|
Definition
No, you can integrate or make an existing system as a business service. Provided that each is loosely coupled and exposed it's functionality. |
|
|
Term
Can you explain business layers and plumbing layers in WS? |
|
Definition
The division is needed to identify a service.
- Business layer: has direct relevance to business as it carries out business functions.
- Plumbing layer: a technical layer which talks about managing computer resources. |
|
|
Term
What is the difference between services and components in WS? |
|
Definition
- Services are logical grouping of components to achieve business functionality.
- Components are implementation approaches to make a service. |
|
|
Term
Can you describe the complete architecture of SOA?
(Definition)(Hint: 5) |
|
Definition
Because the goal of SOA is to connect multiple systems together, they must message each other. ESB acts like a post office which guarantess delivery of a message between systems in a loosy coupled manner.
(Registry, Workflow, Service Broker, Process Manager, SOA supervisor.) |
|
|
Term
What is a end/endpoint? What are the types?
(Hint: 3) |
|
Definition
An endpoint is a connection point where a service can be available to the client.
ABC = Address (where), Binding (how), Contract (what) |
|
|
Term
Can you explain a practical example in SOA? |
|
Definition
An online order system for a companies website. |
|
|
Term
|
Definition
SOA is thinking, it's an architectural concept and web service is one of the technical approach to complete it. Web services are the preferred standards to achieve SOA. |
|
|
Term
What is a reusable service? |
|
Definition
It is an autonomous, reusable, discoverable, stateless functionality that can be part of a composite application or service. A reusable service should be identified with a business activity described by the service specification. |
|
|
Term
Talking about Service identification, which approach between top-down and bottom-up methodologies encourages re-use and maintenance? |
|
Definition
Since the top-down approach is business-driven, it can be practical to separate the different concerns of business and IT of different plans, providing a common ground in between. |
|
|
Term
How can you achieve loose coupling in a SOA?
(Hint: 2) |
|
Definition
- Use the service interface to limit the dependency.
- Encapsulate the service functionalities to limit the impact of changes. |
|
|
Term
The Service of a SOA should be engineered as stateless or stateful? |
|
Definition
Service should be stateless. It may have a context within its stateless execution, but it will not have an intermediary state waiting for an event or a call-back. |
|
|
Term
|
Definition
A infrastructue that implements the SOA concept; which provides mechanism for security, implementing a level of SLA, routing, & transformation capabilities. |
|
|
Term
What are the common pitfalls of SOA?
(Hint: 2) |
|
Definition
- Viewing SOA as an end (its a means to an end).
- Trying to solve multiple problems at once (solve small pieces first). |
|
|
Term
What is the endpoint Contract (what)? |
|
Definition
It defines the protocol of how the client should communicate with the service. |
|
|
Term
What is the endpoint Binding (how)? |
|
Definition
Determines how the endpoint can be accessed and how communication is done. |
|
|
Term
What is the endpoint Address (where)? |
|
Definition
Indicates where we can find this service. It is a URL, which points to the location of the service. |
|
|