Google Service (Dream) Weaver

by Jay Cuthrell
Share and discuss on LinkedIn or HN

Music: Gary Wright - Dream Weaver (1975)

This week we take a look at Google Service Weaver and the next generation of distributed applications.

Getting Informed

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._ [1]

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.

For a great roundup post, check out what Matt Campbell put together over at InfoQ.

https://www.infoq.com/news/2023/03/google-weaver-framework/

Maybe to an astral plane 🎶

Remember that Shakespearian thing about life being a stage and we are but actors? Well, let’s go back to 2009 and learn about “Actors in Erlang”[2] from Alex Miller.

And speaking of weavers and dreams… A quarter century has passed since Macromedia Dreamweaver launched[3] to capture the hearts, minds, and checkbooks of budding web developers in the late 1990s.

Screenshot 2023-03-12 at 4.31.44 PM.png

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.

Meet me on the other side 🎶

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

Screenshot 2023-03-12 at 4.10.58 PM.png

For comparison, buf already has impressive GitHub vanity metrics (as of 12-Mar-2023):

  • 70 Watchers
  • 174 Forks
  • 6,400 Stars

Screenshot 2023-03-12 at 4.14.44 PM.png

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!

_P.S. Special thanks to Neeloy Bhattacharyya for the feedback last week as inspiration to create this issue of Fudge Sunday!_

Disclosure

I am linking to my disclosure.

  1. A Quick Introduction to Service Weaver ↩︎

  2. Understanding actor concurrency, Part 1: Actors in Erlang (2009) ↩︎

  3. Adobe Dreamweaver on Wikipedia
    🤓 ↩︎

Topics:

✍️ 🤓 Edit on Github 🐙 ✍️

Share and discuss on LinkedIn or HN

  • Get Fudge Sunday each week