Are you developing microservices or just considering splitting your monolith? And what is the right way for your services to communicate with each other?
Alex Borysov and Mykyta Protsenko compare gRPC, a modern high-performance RPC framework from Google, and REST, an established architectural pattern, leaving no stone unturned, outlining landmines, and sharing best practices—all to help you determine the right choice for your project. Let’s get ready to rumble!
Alex Borysov is a software engineer at Google, where he works on payments fraud detection infrastructure. Alex is a clean coder and a test-driven developer with solid experience in large-scale software development. He’s passionate about software development process and technologies. Previously, Alex developed trading systems and microservices architecture for leading social casino games and built infrastructure backend services for a unicorn startup in Silicon Valley with 300+ million users.
Mykyta Protsenko is a senior software engineer at Roku. Mykyta is passionate about all things scalable, from coding to deploying to monitoring. He has solid experience building high-performance backends for a variety of applications at leading Silicon Valley companies, including top-rated social mobile games and billing platforms. Mykyta is the author of Henka, a Gradle plugin for Terraform. He’s an occasional speaker at conferences such as Devoxx Belgium, JavaDay Kyiv, and Gradle Summit.
Comments on this page are now closed.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org