DZone Posted February 8 Share Posted February 8 As a quick recap, in Part 1: We built a simple gRPC service for managing topics and messages in a chat service (like a very simple version of Zulip, Slack, or Teams). gRPC provided a very easy way to represent the services and operations of this app. We were able to serve (a very rudimentary implementation) from localhost on an arbitrary port (9000 by default) on a custom TCP protocol. We were able to call the methods on these services both via a CLI utility (grpc_cli) as well as through generated clients (via tests). The advantage of this approach is that any app/site/service can access this running server via a client (we could also generate JS or Swift or Java clients to make these calls in the respective environments).View the full article Quote Link to comment Share on other sites More sharing options...
.png.6dd3056f38e93712a18d153891e8e0fc.png.1dbd1e5f05de09e66333e631e3342b83.png.933f4dc78ef5a5d2971934bd41ead8a1.png)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.