Summary

In this chapter, you learned the differences between REST APIs and gRPC, as well as the advantages when using gRPC with service-to-service communication.

You created a service contract using Protobuf syntax to define services and messages. Contrary to REST, gRPC is strict when it comes to messages and service operations. You created servers and clients using the classes that were generated with the proto files.

To reduce cost in the cloud, it can be cost-effective to use protocols with lower overhead for service-to-service communication. However, other options are available as well. Upon completion of the game, it’s not required to inform the listener immediately. There’s also a price aspect to this: with the current implementation, the live service is running when accessed from the game APIs service. If nobody is listening, this is not required. By using asynchronous communication, the live-service can register to receive information when it’s started...