58 discussions in the community
We recently had an incident where a large bulk import job from one of our tenants consumed all available resources, impacting the performance and avai...
we've got this colossal 10-year-old php monolith. it's got no tests, uses outdated dependencies, and frankly, it's terrifying to touch. management is ...
we're taking a fresh look at how solid principles apply when you're designing distributed systems at scale. single responsibility principle feels pret...
i've become a big proponent of the modular monolith as an often-overlooked middle ground, especially for startups or teams that prematurely jump into ...
We're considering adopting hexagonal architecture (ports and adapters) for a new mid-size service our 5-person team is building. The idea of isolating...
Ensuring reliable event publishing from within database transactions is a common challenge for maintaining data consistency across services. We need t...
Our backend team is heavily invested in an event-driven architecture, which works great for scalability and decoupling. However, our frontend team is ...
My current team is quite strict about following clean architecture principles. While I appreciate the separation of concerns and testability, it feels...
We're exploring CQRS for a new service but want to avoid the full complexity of event sourcing, at least initially. Our thought is to have a tradition...
we're in the process of splitting up a monolith, and the most contentious debates are always around defining service boundaries. everyone agrees on mi...
I'm curious about the current relevance and practical applications of the Actor model (like Akka or Orleans) for building high-concurrency, distribute...
we're dealing with the classic problem of our mobile and web clients hitting the same core APIs, which often leads to bloated responses or inefficient...
i've been advocating for a modular monolith approach lately, especially after seeing several teams at work struggle with premature microservices. they...
we're running Kong as our API gateway at the edge, handling things like authentication, rate limiting, and basic routing for external traffic. however...
our current team follows clean architecture pretty strictly. for even a simple CRUD feature, we end up with controllers, use cases, interactors, entit...
we've been evolving our cache invalidation strategies over the years. initially, we started with simple time-based ttls, usually 5 minutes, but that l...
we recently had a major outage where one tenant's large data import operation consumed all available database connections, effectively taking down the...
our team's been really leaning into clean architecture principles lately, which is great for theoretical purity and testability. the challenge we're r...
we recently had an incident where a single tenant performing a massive data import effectively starved resources for all other tenants in a multi-tena...
we're in the early stages of designing a plugin architecture for our b2b saas platform, similar to how shopify or figma allow extensions. the goal is ...
