Use Asynchronous Calls instead of sync when doing Network calls #76

[markus-gsf-seidl]

Conversion of #76 as the owner seems to have problems with PRs to this repository.

Added the flavour of #108 and made it a cloud pattern, added consideration to cover both.

[aoifefitton]

For initial review:
@srini1978
A few phrasing suggestions:
In the "Solution" section consider changing "lesser energy consumed" to "reducing energy consumption".
In the "SCI impact" section consider changing "hence energy consumed is reduced" to "reducing energy consumption" and also to add full stops to both the E & M sentences.
In the "Assumptions" section a full stop is to be added also.

Otherwise, content/structure looks good.

The referenced existing Cloud Pattern "Optimize average CPU utilization" seems to act as a parent pattern to this one, however I think this pattern may be better suited for the Web section, what do you think @markus-ntt-seidl

[markus-gsf-seidl]

Thanks for your feedback.

Here is my reasoning why I think it's cloud:

Web is by default async and it's hard (if not impossible) to do synchronous calls in the browser.
Whereas in the backend/cloud synchronous patterns are the default - where async would be better. I see a lot of devs doing something like this:

var resultA = callServiceA();
// do something with A
var resultB = callServiceB();
// do something with B (only)

Without any dependencies between A and B this can be easily done async.

One thing that happens in web often is call chaining ( the result-promise of service A would then call service B if A is done). For this there is already a pattern in web to improve this (Avoid chaining critical requests).

[aoifefitton]

@markus-ntt-seidl ok thank you for explaining - Cloud sounds good.

[greenhsu123]

Completed SME review. The content looks good, thanks!