Glossary · architecture
Microservice
Definition
Microservice architecture splits an application into small, independent services. Each service has its own database, deploys independently, and communicates via API or message queue. Netflix, Amazon, and other large-scale systems use this approach.
Detailed explanation
In microservice architecture, each business capability (user management, payment, notification, product catalog) is a separate service. Services can use different languages and databases; teams deploy independently.
Monolith vs Microservice: Monolith is a single codebase, single deploy — fast to start, hard to scale. Microservice enables independent scaling (only the payment service scales), team autonomy, but adds distributed system complexity. Rule: start with a monolith, move to microservices when you need to scale.
Tools: Docker (container), Kubernetes (orchestration), API Gateway (central entry point), Kafka/RabbitMQ (message queue), Istio (service mesh). In Turkey: AWS EKS, Azure AKS, GCP GKE are common.
Use cases
→Large-scale SaaS platform
→High-traffic e-commerce system
→Enterprise app with autonomous teams
→API-first platform economy
→Multi-tenant B2B software
Pros
- +Independent scaling (only bottleneck service)
- +Team autonomy (different tech per service)
- +Fault isolation (one service down, others run)
- +Independent deployment
Cons
- −Distributed system complexity
- −Network overhead (inter-service communication)
- −Distributed tracing + monitoring setup
- −Over-engineering for small projects
Related terms
Related services
Planning a project around Microservice?
In a 30-minute discovery call we share a written architecture + cost + team recommendation tailored to your project.
Start a discovery call