MicroServices

Questions to Be Asked

Eureka

When a new service is introduced, it registers with the service registry.
Services can look up other services through the registry.
There is a single point of failure.
Code needs to be written for each service to interact with the service registry.

Purpose: To address the limitations of service registries by managing service-to-service communication in a more streamlined way.

Data Plane
- Consists of lightweight proxies deployed alongside every instance of your microservices (sidecar pattern).
- Handles all outbound/inbound communications for the instance.
- Example: Using Istio, a popular service mesh, you could deploy the Envoy Proxy on all microservice instances.
Control Plane
- Manages and configures the data plane proxies.
- Configures policies such as retries, rate limiting, health checks, etc.
- Handles service discovery (tracking IP addresses of instances), deployments, and more. Example:
- Envoy (sidecar) manages communication between services, featuring capabilities like circuit breaking, load balancing, and retries.
- Istio (control plane) manages all the Envoy proxies. Resources:
- Quora Engineering - Building a Service Mesh in a Hybrid Environment
- Cilium (handles networking at the kernel level using eBPF, avoids iptables and kube-proxy in Kubernetes)

Recognizing and avoiding common antipatterns in microservices and domain-driven design.

Domain Storytelling: A pictorial representation of the domain story to define bounded contexts.

An architectural pattern where services communicate through events rather than direct calls.
https://hookdeck.com/blog/event-driven-architectrure-fundamentals-*pitfalls*

ReadySet: Real-time SQL caching for Postgres and MySQL that manages everything internally.
- Uses streams and watches for changes.