Abstract
It generally takes lots of time and decisions to create an HTTP API, but when you want to get productive fast, you want to skip as many steps as possible. I’ve been working with gRPC for almost a year and I can guide you from first lines of the code up to request tracking or exposing it via HTTP. When you want to build a usable API these days, you immediately think about creating an HTTP server and you start from there. You may want to use a standard library or a handful of popular libraries that help you with that. What if I told you that there is an alternative? With gRPC you can build fast, elegant and reliable solutions which, in the end, could also be exposed via standard HTTP server. I would like to guide you from the first steps, through various levels of compexity, to request tracking while mainaining an elegant, readable and testable codebase.
