---
tag: microservices
articles: 14 · beats: 3
latest: November 15, 2026
---

Microservices

14 Crashtech articles on Microservices, spanning System Design & Architecture, Development Best Practices and Networking, published between October 2026 and November 2026. Every piece is full-text HTML with sources, structured data and an authored FAQ.

They span System Design & Architecture (10), Development Best Practices (3), Networking (1). System Design & Architecture Development Best Practices Networking

Architectural visualization of a unified GraphQL schema branching into federated microservices with data-flow resolvers.
Development Best Practices3 min

GraphQL Architecture Demystified: Client-Driven Queries, Resolvers and Federation

How GraphQL replaces fixed REST endpoints with flexible typed schemas, solves the N+1 problem with DataLoader, and scales via Apollo Federation.

A mobility engineering team routes model packages to small serving services and checks diagnostics before dispatch.
System Design & Architecture2 min

How Lyft Built LyftLearn Serving: Generated Microservices and Model Self-Tests at Scale

How Lyft serves millions of ML predictions per second: decoupling data and control planes, generating per-team microservices, and model self-tests.

Independent market stalls keep their own ledgers and exchange event envelopes through couriers.
System Design & Architecture3 min

Microservices Architecture: Bounded Contexts, Event-Driven Decoupling and Database Splitting

Architectural guide to splitting monoliths: defining bounded contexts, managing distributed transactions with Sagas, and avoiding microservice sprawl.

System Design & Architecture6 min

Saga Pattern Demystified: Orchestration vs Choreography for Distributed Transactions and Compensating Actions

A comprehensive guide to the Saga pattern: Two-Phase Commit failure modes, compensating transactions, choreography vs orchestration, and idempotency.

Technical isometric comparison of microservice data sharing: shared database anti-pattern vs synchronous API calls vs event-driven messaging
System Design & Architecture6 min

Sharing Data Between Microservices: Shared Databases vs Synchronous APIs vs Event-Driven Messaging

A pragmatic guide to sharing data across microservices: shared databases, synchronous APIs, event-carried state transfer, CDC, and the Outbox pattern.

High-tech isometric visualization of dynamic microservices registering with a central discovery hub with active green health heartbeats.
System Design & Architecture3 min

Service Discovery Demystified: Client-Side vs Server-Side Registration and Health Checks

How dynamic cloud services locate ephemeral instances, compare client-side and server-side discovery patterns, and prevent stale routing tables.

Networking5 min

Service Mesh Architecture: Data Plane Sidecars, Control Plane Traffic Policy, and Zero-Trust mTLS

An architectural guide to Service Mesh: Envoy sidecars, Istio control planes, transparent mTLS, traffic shedding, and ambient eBPF alternatives.

System Design & Architecture3 min

Service-to-Service Communication Patterns: Synchronous vs Asynchronous Protocols

Comparing synchronous REST and gRPC against asynchronous message brokers (Kafka/RabbitMQ) and event meshes in distributed microservice topologies.

System Design & Architecture3 min

12 Core Architectural Concepts: Load Balancing, Caching, Sharding, and Circuit Breakers

A comprehensive architectural reference: load balancing, CDNs, sharding, consistent hashing, rate limiting, circuit breakers, and event-driven queues.

Hands fit a compact metal mechanism into a counter machine while matching blue and orange event streams move through it.
Development Best Practices4 min

Grab’s Counter Service Rewrite: What Go-to-Rust Migration Actually Changed

Grab reports 70% infrastructure savings at similar performance after rewriting a high-QPS Go service in Rust—and documents the async pitfalls behind the result.

A miniature terminal sends several colored client routes through one guarded gateway before they branch to backend services.
System Design & Architecture4 min

API Gateways: What Belongs at the Edge—and What Should Stay in a Service

A sourced guide to gateway routing, authentication and rate limits, with practical boundaries for BFFs and backend business logic.

System Design & Architecture5 min

Backends for Frontends, and What Comes After: Value-Added Services and Domain Gateways

BFFs fix client sprawl, then duplicate authorization logic across themselves. The three-layer fix: edge, value-added services, and per-domain gateways.

System Design & Architecture5 min

Microservices Data Patterns: Database per Service, Saga, Outbox and CQRS

Once each service owns its data, transactions and queries break. Four patterns that put them back, with the failure each one prevents and the cost it adds.

Development Best Practices2 min

Modular Monoliths for Agent Workflows: Where Local Calls Help

Agent workflows amplify needless service hops. Modular boundaries and short transactions simplify execution; remote effects still need durable recovery.

Questions we answer about Microservices

Frequently asked questions

What does Crashtech publish about Microservices?

14 articles tagged Microservices, the most recent published November 15, 2026. They span System Design & Architecture (10), Development Best Practices (3), Networking (1). Each carries numbered sources, an authored FAQ and full structured data.

What questions about Microservices does Crashtech answer directly?

10 questions have a dedicated answer page under this tag, including “What is the N+1 query problem in GraphQL and how is it fixed?”. Each answer is authored prose from the article it belongs to, not a generated summary.

Can AI assistants read Crashtech's Microservices coverage?

Yes. Crashtech serves full static HTML to every crawler, allows all major AI user agents in robots.txt, and publishes an llms.txt manifest plus a full-text corpus, so assistants can retrieve and cite these articles directly.