Why Separate Databases? Explaining Like You're Five - CodeOpinion
I want to give you three different examples and reasons why you might want to separate customers and orders into different databases.| CodeOpinion
I want to give you three different examples and reasons why you might want to separate customers and orders into different databases.| CodeOpinion
Loosely Coupled Monolith is focusing on cohesion, managing coupling, and that logical boundaries aren’t your physical boundaries.| CodeOpinion
How do you know if you should use Domain Driven Design? Does your domain have complexity and require boundaries?| CodeOpinion
In domain-driven design, you might think about aggregates when domain modeling? But often, that approach is backward. Here's why.| CodeOpinion
Want to start with Domain-Driven Design (DDD)? Don't start with sample apps or looking at code. It's the wrong place to start.| CodeOpinion
Database migrations can be tricky, depending on your application and environment. The key is making backward-compatible changes!| CodeOpinion
McDonald's uses Event-Driven Architecture! Here's a breakdown of all the components and how they all work together and why.| CodeOpinion
A common and very overlooked issues when writing a distributed system is consistency. Without it you'll be left scratching your head.| CodeOpinion
The five most common mistakes that make code unmaintainable. As your system grows, it becomes impossible to make changes without breaking.| CodeOpinion
When you need to scale your API, first thought is often, “Let’s just add a cache.” If API Caching were that simple. It's not.| CodeOpinion
I’ve made some architectural decisions I’m proud of and some I definitely regret. Here's what I've learned over the last decade.| CodeOpinion
Something that’s often overused, misunderstood, or just incorrectly applied in software development: Data Transfer Objects (DTOs)| CodeOpinion
What's the biggest scam in tech that is deemed acceptable? Best practices. Everything has trade-offs and your context matters.| CodeOpinion
You might have heard the recommendation to steer clear of static variables or methods. But is that really good advice?| CodeOpinion
So, you're building a system around business processes and workflows. Great! But where does the code go that has to orchestrate all this?| CodeOpinion
Vertical Slice Architecture Myths are a plenty. As with everything that becomes more popular there is misunderstandings that spread.| CodeOpinion
YAGNI is simple: don’t build something today that you assume you'll need in the future. However, we also don’t want to handcuff ourselves.| CodeOpinion
Don't get bogged down by "persistence ignorance". Your data model matters as much as your domain model. Realize they are two different things.| CodeOpinion
Nobody likes working in a brownfield legacy codebase. But is it avoidable? It is! Here's 3 tips for keeping your system evergreen.| CodeOpinion
How do we avoid writing spaghetti code so our systems don't turn into a hot mess? For me, it's focusing on coupling and cohesion.| CodeOpinion
How do you handle long-running HTTP requests that take a long time to complete? Move the work async and return to the client immediately.| CodeOpinion
Need resilience in your system? Look no further than the bulkhead pattern which is about creating isolation in various parts of your system.| CodeOpinion
What are the "best practices" when you design REST APIs? There are a lot that solve problems that you might not need to have.| CodeOpinion
