The Future of Integration
#ICYMI: The subject of integration is often an unloved subject, yet it remains and will remain a core subject. New technologies are emerging without openly shouting that they are integration technologies. I think of the API Management, whose success is not denied, but also others like GraphQL and Data Virtualization. So this is indeed a very actual topic and one that will continue to make headlines. It is, therefore, interesting to ask ourselves what future we can prepare for.
If I had to make it very simple, I would say that the two drivers of integration are the ever-increasing costs of integration and the changing technological landscape. These costs may eventually represent 50% of the costs of major projects according to Gartner. As for the technological evolution, I retain the following points: https://goo.gl/avuGdk
Packaging Generated Code for gRPC Services
#ICYDK: 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/MzejzW