System Architecture · Quick recall Q&A

1 min read
Mid-level7 min read
Rapid overview

Quick recall Q&A

  • Q: When would you prefer a modular monolith over microservices?
  • A: When you need speed, strong consistency, and your team/ops maturity is not ready for distributed complexity.
  • Q: How do you avoid data inconsistency in microservices?
  • A: Use clear data ownership, outbox/inbox patterns, idempotent consumers, and sagas for workflows.
  • Q: What is the purpose of an API Gateway?
  • A: Single entry point for clients providing unified authentication, rate limiting, routing, and protocol translation. Prevents clients from knowing about individual services.
  • Q: How do you implement multi-tenant data isolation?
  • A: Global query filters in EF Core that automatically filter by TenantId. Resolve tenant from JWT claims or headers. Ensure filters cannot be bypassed except by superuser roles.
  • Q: What observability is required for microservices?
  • A: Centralized logging with correlation IDs, distributed tracing (OpenTelemetry), metrics with service-level dashboards, and health check endpoints for orchestrators.
  • Q: Why is event-driven architecture common in trading systems?
  • A: Market data and trades are naturally streams of events, and async pipelines handle bursts without blocking request paths.

See also