#ICYMI: This is the second post in a series on how we scaled Bugsnag’s new Releases dashboard backend pipeline using gRPC. Read our first blog on why we selected gRPC for our microservices architecture.
For the launch of the Releases dashboard in Bugsnag, we undertook a massive project to scale our data-processing Pipeline and break it down into microservices. As you may have read previously, we selected gRPC as our communication framework that would allow our services to talk to each other, and we began the process of defining the Protocol Buffers necessary to support the gRPC API. Not only does gRPC use the blazingly fast HTTP/2 binary protocol, but it also makes use of Google’s Protocol Buffers; a major reason for choosing gRPC. https://goo.gl/b1NjHH
Share this:
- Click to share on Facebook (Opens in new window)
- Click to share on Twitter (Opens in new window)
- Click to email a link to a friend (Opens in new window)
- Click to share on LinkedIn (Opens in new window)
- Click to share on Tumblr (Opens in new window)
- Click to share on Pinterest (Opens in new window)
- Click to share on Reddit (Opens in new window)