Because you will save yourself a great deal of money.
Microservices repeated SOA’s mistakes almost move for move — the technical decoupling was easy, the organizational decoupling never happened, and both efforts failed the same way a decade apart. gRPC is CORBA’s direct intellectual descendant, and it succeeded precisely where CORBA failed by narrowing its scope instead of trying to be everything. The industry rediscovers service discovery, schema registries and contract-first design roughly every eight years, each time with a new name and no memory of the previous attempt.
History also corrects the triumphalist story this field tells itself, which is that each new style obsoletes the last. RPC did not die and then come back; it was always there. REST did not replace everything; it became the pragmatic center of a diverse toolbox. SOAP is not gone; it is running in production in most large enterprises right now.
The practical use of all this is calibration. When someone tells you a new protocol changes everything, knowing what happened the last four times lets you ask the right question — which is not “is this real?” but “what is the narrow context where this genuinely fits, and what will it cost when it is used outside that context?”