Balancing microservices and a compute-core for a latency-critical risk engine

[StephenJ]

I'm a senior engineer at a financial services firm, and we're in the early stages of migrating a critical, monolithic risk calculation engine to a cloud-native architecture. The current system is a massive C++ application that runs on-premises, and while it's incredibly fast for batch processing, it's inflexible, expensive to scale, and a nightmare to deploy updates to. The business wants to move to a microservices model on AWS to improve agility and enable real-time risk analytics. However, we're facing a major dilemma: the core calculation algorithms are highly sensitive to latency and require tight coupling between data ingestion, transformation, and computation steps. Initial prototypes using event-driven, fully decoupled services have introduced unacceptable overhead, adding hundreds of milliseconds to calculations that need to complete in under fifty. The team is now considering a hybrid approach—keeping a tightly integrated "compute core" as a single, scalable service while breaking apart the supporting data pipelines and UI layers. I'm concerned this might just recreate a distributed monolith with all its complexities. For architects who have modernized similar high-performance, low-latency systems, how did you approach the decomposition? Did you find that strict microservice boundaries were incompatible with your performance requirements, and if so, what patterns did you use to isolate domains without sacrificing speed? How did you validate the performance of your new architecture before committing to a full rewrite?

[JasonRJ]

Beware of morphing into a distributed monolith; keep cross-service calls lean and purposeful. Use the strangler pattern to decompose only the non-hot paths first, maintain a single source of truth for critical state, and design idempotent operations so retries don’t explode state.

[Anthony98]

You're not alone. The pragmatic path is hybrid: keep the compute core tight, expose it through a fast boundary, migrate other pieces behind that boundary with strangler steps. Set a strict latency budget on the boundary to prevent slowdowns and keep the critical path predictable.

[LunaS]

Rollout gating: establish kill switches and rollback plans, stage the rollout from lab to production, and keep the old path available until you have confidence in the new boundary. Document risk, decision criteria, and exit criteria so stakeholders can follow the plan.

[Tyler_S]

Here's a concrete 6-step plan I’ve used: 1) map hot data paths and set strict per-step latency budgets; 2) define a minimal, stable API surface for the compute core; 3) build a lightweight gateway (gRPC preferred) to translate inputs/outputs; 4) roll out behind a feature flag; 5) run a 4–6 week pilot with representative workloads; 6) compare end-to-end latency, throughput, and SLO adherence against the baseline and make a go/no-go decision.

[Timothy_R]

Testing beyond chaos: build a latency model, deterministic replay engine, and shadow deployments where the new logic runs in parallel and outcomes are compared. Do end-to-end benchmarks with realistic workloads and validate invariants (ordering, exactly-once semantics) before going live.

[NoraG]

Question: what are your target boundary latency budgets (e.g., 1–2 ms), whether you’ll cross region boundaries, and what stack you’re using (Kubernetes, EC2, or serverless)? Sharing rough numbers will help tailor a concrete 4–6 week validation plan and a boundary architecture diagram.