The BEST gRPC Framework for Golang

Подписаться 27 тыс.

Просмотров 6 тыс.

50% 1

In this video I talk about my favorite Go RPC framework, Twirp. It was made by Twitch and is open source. Definitely check it out, its a reliable alternative to gRPC (even though it's also great!)
Links:
github.com/twitchtv/twirp
twitchtv.github.io/twirp/docs...
Code: github.com/Melkeydev/go-bluep...
Video Editor: @TheMason
Twitch
I stream live on Twitch every weekend
Twitch : / melkey
Join the amazing community on Discord
Discord: / discord
I post memes and host Twitter Tech Spaces
Twitter: / melkeydev
Unlock the power of modern backend development with Go in this quick guide to Twirp and gRPC. Discover how these tools streamline creating efficient, scalable server applications. Perfect for developers looking to enhance their backend skills!
The BEST Golang RPC Framework (not gRPC)
This Is My FAVORITE Golang + RPC Framework (not gRPC)
The EASIEST Golang + RPC Framework to Use
How I Build With Golang + RPC in Production
SUBSCRIBE OR GET LAID OFF
╔═╦╗╔╦╗╔═╦═╦╦╦╦╗╔═╗
║╚╣║║║╚╣╚╣╔╣╔╣║╚╣═╣
╠╗║╚╝║║╠╗║╚╣║║║║║═╣
╚═╩══╩═╩═╩═╩╝╚╩═╩═╝
#coding #neovim #typescript #programming #vim #softwareengineering #codinglife #webdesign #webdevelopment #webdev #javascript #rustlang #rust #twitch #twitchstreamer #programmerhumor #codinghumor #software #softwareengineer #softwaredeveloper #softwaredevelopment #gymbro #gym #programmerhumor #programming #coding #golang #go #golanguage

Наука

Опубликовано:

6 май 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 18

@beneditomauroo 11 дней назад

Please start doing timestamps in the video 🙏🏾

@themddropout6141 День назад

Just to clarify for anyone learning about this, Twirp is NOT a framework on gRPC. Twirp is a Go RPC framework, not to be confused with gRPC. Melkey mentions this in the description but just pointing it out more explicitly for anyone learning. Both share some similarities in their approach to improving RPC systems. Both use proto files to define service interfaces and message types, and generate client and server stubs. However, they use different transport protocols and serialization formats: - gRPC uses HTTP/2 and uses only protobuf for binary serialization - Twirp uses HTTP/1.1 and uses both protobuf and json for serialization

@bsquidwrd 12 дней назад

This was a great intro into twirp and gRPC! Been thinking about using this lately and was kinda lost on how to get started, so this is perfectly timed!

@MelkeyDev 12 дней назад

Glad it was helpful!

@ysomad 10 дней назад

there is also connect-go which implements streaming also and uses generics so the amount of generated code is so small, created by buf

@0xtz_ 12 дней назад

that's cooool man 😎 great video

@MelkeyDev 12 дней назад

Glad you enjoyed

@joeldickson5471 6 дней назад

Protobuff + twerp sounds a lot like open api + open api generator

@ThirdWorldDev 3 дня назад

I've been trying to learn gRPC lately and this was such a great into! Thank you so much. One thing that was not clear for me on the video is the differences between using just gRPC and using Twirp. Can you explain that a little bit? Another question: when working with GraphQL or REST APIs, it's easy to find out about the route using GQL self-generated docs or Swagger in case of REST. Is there something similar for gRPC? And yet another one: you mentioned that gRPC is a different protocol than HTTP. I thought that gRPC (and Twirp) used HTTP 1.1 behind the scenes. Am I missing something or did I misunderstood? Thanks again for the great video!!

@themddropout6141 День назад

Twirp is NOT a framework on gRPC. Twirp is a Go RPC framework, not to be confused with gRPC. Melkey mentions this in the description but just pointing it out more explicitly for anyone learning. Both share some similarities in their approach to improving RPC systems. Both use proto files to define service interfaces and message types, and generate client and server stubs. However, they use different transport protocols and serialization formats: - gRPC uses HTTP/2 and uses only protobuf for binary serialization - Twirp uses HTTP/1.1 and uses both protobuf and json for serialization