Google Service (Dream) Weaver
This week we take a look at Google Service Weaver and the next generation of distributed applications.
Last week we looked at buf. Now, let’s talk a bit about the potential implications of a blog post announcing Google Service Weaver from Srdjan Petrovic, Garv Sawhney, Urs Hölzle, Parveen Patel, Mark Lohmeyer, Amin Vahdat, Michael Whittaker, Robert Grandl et al.
There’s a website: https://serviceweaver.dev
There’s a /docs.html (well done): https://serviceweaver.dev/docs.html
There’s a hello world blog too: https://serviceweaver.dev/blog/quick_intro.html
This will probably catch your eye…
_We found out that Service Weaver improves application latency by 15x and reduces VM costs by 9x when compared to a typical microservices solution built on top of gRPC and protocol buffers._ 
So, I don’t have any inside knowledge — but it is safe to say that Service Weaver didn’t just come into existence a few weeks ago. This problem space is very likely an _old itch_ that got _scratched within Google_ and now _the “new” backscratcher_ is being shared with all.
Google has released Service Weaver, an open-source framework for building and deploying distributed applications. The Go-based framework includes a set of programming libraries that enable writing applications as a single modular binary. The other component is a set of deployers that allow for confi…
And speaking of weavers and dreams… A quarter century has passed since Macromedia Dreamweaver launched to capture the hearts, minds, and checkbooks of budding web developers in the late 1990s.
A few years after capturing everything Microsoft had not already captured in the web authoring tools market, Macromedia became part of Adobe in 2005.
What can we draw from the comparison of a “new” framework meant for building and deploying distributed applications to a 90s era web focused integrated development environment (IDE)? Well, I don’t know, yet — not for sure by any means.
The Service Weaver potential for “a better way” will be interesting to watch over the next three (3) years or so. In just a few months, Service Weaver has gathered impressive GitHub vanity metrics (as of 12-Mar-2023):
- 41 Watchers
- 94 Forks
- 2,800 Stars
For comparison, buf already has impressive GitHub vanity metrics (as of 12-Mar-2023):
- 70 Watchers
- 174 Forks
- 6,400 Stars
Graphs like these can be easily conflated with patterns for success in tooling. In reality, these graphs are looking backwards at what might be a trailing indicator of success in tooling.
Ultimately, as Lee Ditiangkin might argue, growth in adoption comes from making a strong business case that happens to include tooling which improves key metrics used for measuring developer experience.
So, what will be the next big thing in distributed applications?
Until then… Place your bets!
As a reminder, after a +25 year walkabout, I’m an IBMer (again). For 2023, in “Work Plug”, I’ll share a new link each week that is educational, accessible, and relevant to platform engineering from fellow IBMers in the wider IBM Community.
More Links of the Week:
- Breaking legacy programs into microservices without breaking anything (🧑🏫 Video)
- What is generative AI, what are foundation models, and why do they matter? (📝 Blog)
- Exploring Generative AI to maximize experiences, decision making, and business value (📝 Blog)
- A valuable and responsible approach to AI (📝 Blog)
- How can Generative AI drive disruptive value? (📺 Webinar)
I am linking to my disclosure.