gRPC vs REST: let the battle begin! by Alex Borysov & Mykyta Protsenko
Subscribe to Devoxx on YouTube @ https://bit.ly/devoxx-youtube
Like Devoxx on Facebook @ https://www.facebook.com/devoxxcom
Follow Devoxx on Twitter @ https://twitter.com/devoxx
Let's get ready to rumble! Are you developing microservices or just considering splitting your monolith? Thinking what is the right way for your services to communicate with each other? gRPC is a modern high performance RPC framework backed by Google, while REST is an established architectural pattern for designing distributed systems. We will discuss pros and cons of each approach, going deep and wide, leaving no stone unturned, outlining landmines and showing best practices. In the end the audience can decide what is the right choice for them and their projects.
# Alex Borysov
Software engineer with solid experience in large scale software development. Passionate about software development process and technologies.
Developed trading systems; microservices architecture for World leading social casino games; built infrastructure backend services for a unicorn startup in Silicon Valley with 300+ million users.
Currently working on payments fraud detection infrastructure at Google. Clean coder, test-driven developer.
# Mykyta Protsenko
Software engineer passionate about all things scalable - from coding to deploying to monitoring.
Solid experience in building high-performance backends for a variety of applications in leading Silicon Valley companies: from top-rated social mobile games to billing platforms.
Author of Henka (Gradle plugin for Terraform, https://github.com/roku-oss/henka).
Видео gRPC vs REST: let the battle begin! by Alex Borysov & Mykyta Protsenko канала Devoxx
Like Devoxx on Facebook @ https://www.facebook.com/devoxxcom
Follow Devoxx on Twitter @ https://twitter.com/devoxx
Let's get ready to rumble! Are you developing microservices or just considering splitting your monolith? Thinking what is the right way for your services to communicate with each other? gRPC is a modern high performance RPC framework backed by Google, while REST is an established architectural pattern for designing distributed systems. We will discuss pros and cons of each approach, going deep and wide, leaving no stone unturned, outlining landmines and showing best practices. In the end the audience can decide what is the right choice for them and their projects.
# Alex Borysov
Software engineer with solid experience in large scale software development. Passionate about software development process and technologies.
Developed trading systems; microservices architecture for World leading social casino games; built infrastructure backend services for a unicorn startup in Silicon Valley with 300+ million users.
Currently working on payments fraud detection infrastructure at Google. Clean coder, test-driven developer.
# Mykyta Protsenko
Software engineer passionate about all things scalable - from coding to deploying to monitoring.
Solid experience in building high-performance backends for a variety of applications in leading Silicon Valley companies: from top-rated social mobile games to billing platforms.
Author of Henka (Gradle plugin for Terraform, https://github.com/roku-oss/henka).
Видео gRPC vs REST: let the battle begin! by Alex Borysov & Mykyta Protsenko канала Devoxx
Показать
Комментарии отсутствуют
Информация о видео
Другие видео канала
GraphQL, gRPC or REST? Resolving the API Developer's Dilemma - Rob CrowleyIntro to gRPC: A Modern Toolkit for Microservice CommunicationDesign Microservice Architectures the Right WayThe Story of Why We Migrate to gRPC and How We Go About It - Matthias Grüter, SpotifyMicroservices Data Patterns: CQRS & Event Sourcing by Edson YanagaProtocol Buffers Crash CourseIntro: Envoy - Matt Klein & Constance Caramanolis, LyftRedis at Lyft: 1,000 InstancesgRPC over HTTP/3 is finally a thing | Backend Engineering ShowEvent Sourcing You are doing it wrong by David SchmitzMastering Chaos - A Netflix Guide to MicroservicesBest Practices for (Go) gRPC ServicesNate Barbettini – API Throwdown: RPC vs REST vs GraphQL, Iterate 2018Introduction to gRPC: A general RPC framework that puts mobile and HTTP/2 first (M.Atamel, R.Tsang)The hardest part of operating a service mesh: Envoy ProxyConfusion in the Land of the Serverless • Sam Newman • GOTO 2018Oktane17: Designing Beautiful REST + JSON APIsCommon API security pitfalls by Philippe De RyckREST API vs gRPC, which one should you use in breaking a monolith (Vladimir Dejanov)gRPC Crash Course - Modes, Examples, Pros & Cons and more