What are three characteristics of services in the proposed Service Oriented Architecture? (Choose three

A company has contracted a developer to create their new accounting system. The system the developer will replace runs a monolithic web application using one web server and one database server. Technical requirements state the developer must write the business logic in Java, deploy to the application server and push the presentation logic onto the web servers. What are three characteristics of services in the proposed Service Oriented Architecture? (Choose three.)

A company has contracted a developer to create their new accounting system. The system the developer will replace runs a monolithic web application using one web server and one database server. Technical requirements state the developer must write the business logic in Java, deploy to the application server and push the presentation logic onto the web servers. What are three characteristics of services in the proposed Service Oriented Architecture? (Choose three.)

A.
Services are coarse grained.

B.
Services are finely grained.

C.
Services are loosely coupled.

D.
Services are tightly coupled.

E.
Clients must be implemented in the Java technology.

F.
Services are platform agnostic, network-addressable web APIs.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


leo yu

leo yu

web service are coarse grained, loosely coupled and network addressable. But I believe that the question is web application not web service.

Mohamed Fayek Saber

Mohamed Fayek Saber

Coarse-grained: A few ojects hold a lot of related data that’s why services have broader scope in functionality. Example: A single “Account” object holds the customer name, address, account balance, opening date, last change date, etc. Thus: Increased design complexity, smaller number of cells to various operations

Fine-grained: More objects each holding less data that’s why services have more narrow scope in functionality. Example: An Account object holds balance, a Customer object holds name and address, a AccountOpenings object holds opening date, etc. Thus: Decreased design complexity , higher number of cells to various service operations. These are relationships defined between these objects.

1. This SOA feature depends greatly on the services being constructed and exposed with coarse-grained interfaces.

2.The concept of loose coupling within SOA is directly influenced by the object-oriented design paradigm,[4] whereby the objective is to reduce coupling between classes in order to foster an environment where both the classes

3.agnostic services are not aware of the context in which they are being called, nor are they aware of how the service is implemented, which platform, technology etc.