We’re back! And not just us, but we’ve brought another guest writer with us; our dear colleague and a Go wizard Jimmy Fagerholm. He will enlighten you about how microservices communicate with gRPC. Enjoy the comeback episode of Fortnightly Dev!
🚀 Shuttle.rs – shuttle.rs
You’ve heard of infrastructure as code. How about infrastructure from code? Still in its alpha, Shuttle.rs provides an alternative approach to creating serverless infrastructure. Build your serverless functions with Rust, annotate said functions using Shuttle’s syntax and voila, you’ve got a working setup. We haven’t used Shuttle yet, but we’d love to hear of your experiences with it.
🥯 Bun – bun.sh
🍋 A Fresh web framework – fresh.deno.dev
🌙 Develop the web without reinventing the wheel – moonzoon.rs, an interview with the developer
Don’t you just love building web applications and dealing with all the same complexity every time? MoonZoon is a full stack framework which has a different take on building web apps and handles challenges like authentication, querying, SEO and the database layer for you. It promises less playing around with tools and configuration so you can focus on what’s important. MoonZoon development is done using Rust, the best programming language.
🏎 gRPC – A high performance, open source universal RPC framework – grpc.io
How do microservices communicate? Some with REST, some with graphQL and others with gRPC.
gRPC takes advantage of Protocol Buffers (protobuf) to define the service API. With the help of the protobuf definitions, you can easily generate idiomatic client and server stubs, in almost any language. Once generated the endpoints can be called like any other method in your code, independent of where your server is located or in which language it’s written. Thanks to HTTP/2-based transport gRPC enables bi-directional streaming and fully integrated pluggable authentication. On top of that, gRPC can be 7 to 10 times faster than REST thanks to HTTP/2 and the tight packing of protobufs.
A few more minutes with tech news? Read the previous volume Fortnightly Dev Vol. 6.