39 discussions in the community
in our microservices setup, we preach independent scaling and deployment. but in practice, i've noticed that scaling up one service often requires sca...
everyone preaches independent microservice scaling, and i get it in theory. but in practice, at least for us, it rarely feels truly independent. if ou...
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...
we've been rolling out opentelemetry across 25 of our core services for the last six months, and the results are pretty interesting. on the good side,...
we're running into a classic microservices dilemma: shared libraries vs code duplication. we have a lot of common code for things like logging, authen...
we're running Kong as our API gateway at the edge, handling things like authentication, rate limiting, and basic routing for external traffic. however...
we're at a point with about 30+ microservices where we're seeing inconsistent retry logic, manual timeouts everywhere, and no standardized circuit bre...
we're constantly dealing with event schema evolution across our data pipelines. adding new fields is usually fine if consumers are resilient, but remo...
We're in the process of decomposing a large monolith into microservices, and we're trying to use Domain-Driven Design (DDD) to define our bounded cont...
our team recently completed a migration of about 15 inter-service APIs from REST over HTTP/1.1 to gRPC over HTTP/2. the primary driver was P99 latency...
In theory, microservices promote independent scaling and deployment. You can scale your user service without touching your product catalog. In practic...
with netflix hystrix deprecated, our team is looking for a modern alternative for implementing the circuit breaker pattern. we heavily relied on it fo...
Event schema evolution is a recurring nightmare for us. We started with simple JSON messages, and it was fine until we began adding, removing, or rena...
my team is facing the classic shared library vs. code duplication dilemma in our microservices architecture. we have about 20 services, and there's a ...
we're in the process of breaking apart a substantial monolith, and the team is constantly debating how small a microservice should actually be. some a...
testing interactions between microservices feels like a huge challenge. unit tests and integration tests for individual services are fine, but how do ...
we just finished migrating about 15 core services from rest to grpc for inter-service communication, and it's been a mixed bag. on the one hand, we've...
We're in the process of decomposing a large monolith using Domain-Driven Design principles, and we're struggling with where to draw the boundaries for...
data ownership in a microservices architecture is a constant source of debate for us. services like authentication, user profile, billing, and notific...
testing interactions between microservices is a constant challenge for us. unit tests are great, but they don't catch integration issues. we're using ...
