· Brittany Ellich · illustration  · 1 min read

How microservices are born

A four-panel comic. The first one is a developer holding a thing and saying "This lives in one of your services, where should I put it?" then the payments team saying "That's not our domain, that's a product concern", then the product team saying "That's not us, that's a payments problem", and finally the developer putting the thing in a new service saying "I guess this goes here then". The text at the end says "And that is how microservices are born".

Based on a true story

Previous

0 Likes on Bluesky

Likes:

  • Oh no, no likes, how sad! How about you add one?
Like this post on Bluesky to see your face show up here

Comments:

  • Oh no, no comments, how sad! How about you add one?
Comment on Bluesky to see your comment show up here
Share:
Back to Blog

Related Posts

View All Posts »
I guess I'm AI-pilled now?

I guess I'm AI-pilled now?

I went from brain dump to a working productivity tool in a single day. Here's how listening to the How I AI podcast pushed me to finally experiment with personalized software, MCP, agents, and skills—and why I think it's time to get on board (with some caveats).

AI Has an Image Problem

AI Has an Image Problem

I spent 2025 going from skeptical to genuinely excited about AI tools. My non-tech friends and family spent 2025 learning to hate them. The AI industry has fumbled this introduction so badly that we've turned a useful set of tools into a cultural flashpoint - but the damage isn't irreversible.

2025 in review

2025 in review

2025 was my year of doing ALL the things - speaking at 5+ conferences, starting a podcast, shipping side projects, and somehow not completely burning out. I learned that momentum creates more momentum, perfectionism is overrated, and seeing people in real life again after years of isolation is actually really, really good.

Representing groups in ATProto

Representing groups in ATProto

I wanted to add book clubs to my GoodReads-like app (Collective), but ATProto doesn't have a standard way to handle shared group resources yet. So I'm building opensocial.community—a separate service that manages groups independently from any single app. This means the same book club could potentially work across multiple apps (imagine your book club having both a reading list in Collective AND a discussion forum in another app), and groups can migrate between providers if needed. It's probably over-engineered for my use case, but might help other ATProto developers building community features.