👑 Context is King 💻 Software Architecture & Design 📺 piped.video/@codeopinion
Canada
- Tweets 11,933
- Following 213
- Followers 12,003
- Likes 6,929
Multi-Tenant "Best Practices" often hide trade-offs. Where complexity really goes when using tenant context, shared databases, filtering, and feature flags.
1
6
719
Don't expose internal domain events across service boundaries. When you treat domain events as your public integration contracts, you couple consumers to your internal domain model and workflows, leading to breaking changes and a fragile system that's hard to change.
2
10
1,023
Why is crap on here? The accounts that post the same engagement crap over and over (1 day apart).
4
5
1,685
Event driven architecture doesn't mean you aren't coupled. Especially when your events are really just database changes being broadcast over a message broker.
1
8
902
I keep reading this is "REST". This isn't going "back to REST". It's going stateless. Which REST is, but devs think of REST as JSON over HTTP and forget everything else. I feel like we're in a world that's about to reinvent a ton of shit.
Before, running a remote MCP server meant managing session state, which limited where you could run it.
Now that MCP is stateless, you can deploy on serverless and edge infrastructure, or scale horizontally behind any load balancer.
4
2
15
2,165
The worst enterprise software decisions often look like "best practices". Here are 5 architecture decisions that create complexity, coupling, and systems nobody can safely change.
2
15
2,730
Multi-Tenancy isn't really about choosing between a shared database or database per tenant.
1
4
43
4,338
Friendly reminder: I have a YouTube channel that is 30 subscribers away from the useless 100k-subscriber vanity metric.
piped.video/@CodeOpinion
1
1
6
522
I hold nothing back when telling whatever model that it's generating a turd pile. The moment it says a "cleaner approach", you know what's going to come up with will be equally terrible.
1
8
1,182
I'll leave this right here... piped.video/watch?v=Bxf_HMs7…
Desktop users with scheduled tasks who are in a timezone that observed daylight saving time were affected by an infinite loop. When the app tried to locate tasks scheduled during the “skipped” hour, it couldn’t resolve them and got stuck.
Download 1.1.5749 at claude.com/download to get the fix.
Sorry for the disruption everyone.
2,083
Giveaway! Awesome people at Particular Software are doing a giveaway for CodeOpinion viewers! Interested in learning more about Distributed Systems Design? Enter for a chance to win a 5 day Advanced Distributed Systems Design course led by Udi Dahan founder of Particular Software, and creator of NServiceBus. Enter here: go.particular.net/2026/codeo…
1
2
3
995
I'd like a system prompt for all my platform feeds to not show me infographics. If it has 100s of likes and comments "solid list.." or "great share", it's a dumpster fire and I don't need to see it.
2
5
1,000
I'm tempted to make a YT video on the pure idiotic X posts that are "questions" and the replies/answers. If you follow this stuff...
4
8
893
Someone is impersonating me. If you receive a message like this on Discord or elsewhere, it is not from me. Just gross.
4
10
2,180
47 Microservices… for 2 Requests Per Second?!
A Reddit post from r/softwarearchitecture that perfectly captures the insanity and also the lack of context about scaling. But scaling what?
piped.video/OoolGJnCq4s
4
4
42
16,885
Feels appropriate to link to the conversation we had about this amongst other things.
piped.video/KfBvR4jx2_g
I’m always surprised when developers are unaware of the tradeoffs they are making by choosing a particular architecture for their applications. Following best practices dogmatically or picking patterns based on buzzwords is the best way to end up in this predicament.
2
11
8,950
Yes, it can get out of hand, and you don't need to copy/distribute data everywhere. As Kelly points out, the "need" is for query purposes, which is a legit use case, but there are a bunch of options.
piped.video/watch?v=NM02lTt0…
I’ve seen some micro service implementations where the micro service obviously owns its data in its own database but also gets replicated data from other micro services to facilitate reads or parent joins.
Customer table is replicated to 6 diff DBs.
This gets out of hand, no?
1
8
2,158
“We switched to Event-Driven Architecture... and now we can’t debug anything.”
That quote from a blog post might sound familiar if you’ve ever tried to replace everything with events.
piped.video/watch?v=sNaFG_b5…
2
5
48
5,358
"Aggregates are dumb! A group chat that can't have more than 100k members"
Stop modeling relationships, model rules.
piped.video/ZvY5fREVyZk
2
27
3,844
If you've ever felt overwhelmed trying to apply DDD, you're not alone. Many devs over-engineer simple parts of their system and ignore the core business workflows where DDD actually shines.
piped.video/watch?v=YTydbtFG…
3
6
73
6,299
It's less about "smart vs dumb devs" and more about design choices and trade-offs.
piped.video/watch?v=FR64isPs…
3
2
23
4,646
Your API isn’t just code—it’s a contract with your consumers. Leaking internals is the fast track to building a fragile system that breaks clients. Think of your API as an ACL (Anti-Corruption Layer) and build stable, evolvable systems
piped.video/watch?v=0IKSU-TK…
1
1
9
1,508
Sat down with @davidfowl to get his thoughts on Design, APIs, and Avoiding Dogma. A lot of insights packed into 30 minutes!
piped.video/watch?v=KfBvR4jx…
10
68
10,643
If you’re working in a system that’s hard to change, it can be frustrating. Making a change in one part causes a bug or some negative side effect in another part that you had no idea about. What's the solution? Look at your database as the root cause.
codeopinion.com/database-cou…
1
15
926
Talked with Gene Kim (author of The Phoenix Project and The DevOps Handbook) about Vibe Coding. But the real mind-blowing moment? His insights on modularity, boundaries, and coupling—and how they create real-world option value in system design.
2
28
1,732
If you’ve ever been told “don’t inject anything into your domain,” this one’s for you. Double dispatch is often misunderstood, especially when it comes to injecting behavior into your domain model.
5
2
38
2,433
Where should authorization live in your software architecture? Should it be inside the domain model if you're using Domain-Driven Design (DDD)? Or should authorization always stay in the application layer?
5
10
45
2,501
"Vibe Coding Rules"... you mean general software development guidelines?
It sure seems like we're baking the same cake with different frosting. (Or it's just pure engagement bait.)
1
5
23
2,051
Are you tired of APIs returning 200 OK… with an error inside? Or vague 400 responses that leave clients guessing what went wrong? I don't even care if you choose not to use ProblemDetails; just be explicit on success/failure and provide meaningful machine—and human-readable responses.
1
1
25
1,703
You might think using regex is enough to validate an email address, but that’s only half the battle. A service I use changed their email validation on my account, which caused me a lot of pain and wasted time.
2
13
983
Yes, you're determining the offset of a future date according to today's rules, which could change in the future before that date arrives. I created this awhile ago.. piped.video/watch?v=Bxf_HMs7…
1
42
Microservices emphasized using separate databases for each service. But is that really helpful? It causes a lot of extra complexity. In the example of e-commerce, you likely want the customer and order data together so you can query it easily. That sounds reasonable, but there is more at play on when and why you might want to separate data.
4
2
32
3,083
Loosely Coupled Monolith - 2025 Edition
The foundation of software architecture and design revolves around coupling and cohesion. Almost everything boils down to it, including the trade-offs around managing coupling and cohesion. One method is what I call the Loosely Coupled Monolith. It focuses on cohesion, manages coupling, and makes the distinction that logical boundaries aren't physical boundaries.
3
5
33
2,029
Database migrations can be tricky depending on your application and environment. Here are some strategies to keep your application code and database schema in sync, allowing smooth deployments and safe rollbacks. The key is making backward-compatible changes!
2
17
1,295
