What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?

Correct Answer: A higher number of discoverable API-related assets in the application network.

*****************************************

>> We do NOT get faster response times in fine-grained approach when compared to coarse-grained

approach.

>> In fact, we get faster response times from a network having coarse-grained APIs compared to a

network having fine-grained APIs model. The reasons are below.

Fine-grained approach:

1. will have more APIs compared to coarse-grained

2. So, more orchestration needs to be done to achieve a functionality in business process.

3. Which means, lots of API calls to be made. So, more connections will needs to be established. So,

obviously more hops, more network i/o, more number of integration points compared to coarse-

grained approach where fewer APIs with bulk functionality embedded in them.

4. That is why, because of all these extra hops and added latencies, fine-grained approach will have

bit more response times compared to coarse-grained.

5. Not only added latencies and connections, there will be more resources used up in fine-grained

approach due to more number of APIs.

That's why, fine-grained APIs are good in a way to expose more number of resuable assets in your

network and make them discoverable. However, needs more maintenance, taking care of integration

points, connections, resources with a little compromise w.r.t network hops and response times.