CoffeeJUG

#REST or #gRPC? I want it all, and I want it now (Part 1) at #coffeejug Speaker Serge Bishyr Team Lead/Software engineer @ #Lohika gRPC became more and more popular. It has a set of advantages over REST. However, support of gRPC in the browsers is not mature enough. It would be great to have gRPC for interservice communication but REST for client-to-service communication. Do we have to implement our API twice? Short answer: No. Agenda:👇 00:00 - intro 01:19 - REST API 05:00 - Protocol Buffers 06:20 - gRPC vs REST API 07:04 - demo project intro 07:16 - CRUD using gRPC 18:00 - Streaming using gRPC 29:30 - headers in gRPC. Interceptors 33:36 - Q&A session CoffeeJug - monthly events for #Java professional (#javausergroup). Follow us on social media: Facebook: https://www.facebook.com/coffeejug.meetup/ Instagram: https://www.instagram.com/coffeejug.meetup/ YouTube: https://www.youtube.com/channel/UCQ65oHlDUUCDCOSgz4rdKZw?guided_help_flow=3 LinkedIn: https://www.linkedin.com/company/coffeejug/

#REST or #gRPC? I want it all, and I want it now (Part 2) at #coffeejug Speaker Serge Bishyr Team Lead/Software engineer @ #Lohika gRPC became more and more popular. It has a set of advantages over REST. However, the support of gRPC in the browsers is not mature enough. It would be great to have gRPC for interservice communication but REST for client-to-service communication. Do we have to implement our API twice? Short answer: No. Agenda:👇 00:00 intro 00:26 let’s use gRPC only? 02:09 ideal scenario 03:38 demo time 41:19 summary 44:50 q&a session CoffeeJug - monthly events for #Java professional (#javausergroup). Follow us on social media: Facebook: https://www.facebook.com/coffeejug.meetup/ Instagram: https://www.instagram.com/coffeejug.meetup/ YouTube: https://www.youtube.com/channel/UCQ65oHlDUUCDCOSgz4rdKZw?guided_help_flow=3 LinkedIn: https://www.linkedin.com/company/coffeejug/