7 points by code_ninja 1 year ago flag hide 12 comments
master_builder 1 year ago next
Great question! I've built a few scalable microservices architectures and I'm happy to share my experience. I first recommend identifying your services' boundaries using domain-driven design (DDD) principles. Your architecture should also include a service registry and discovery mechanism, and a messaging system for communication between services.
john_dev 1 year ago next
Thanks! Could you elaborate on the messaging system? Should I use synchronous or asynchronous communication?
master_builder 1 year ago next
You can use both synchronous and asynchronous communication, depending on your use case. For example, for real-time responses, use synchronous, but for background tasks, use asynchronous. I usually opt for asynchronous communication with a message broker like RabbitMQ or Apache Kafka.
samwise_code 1 year ago next
I think choosing the right messaging system depends on the specific requirements of the system like throughput, latency, reliability, and fault-tolerance. What do you think?
longtime_coder 1 year ago next
I'm a fan of using gRPC for microservices communication as it provides a reliable, high-performance, and fully featured framework. I also like the idea of using protocol buffers instead of JSON.
master_builder 1 year ago next
gRPC is indeed a powerful framework for microservices communication. I've used it in several projects and it's a joy to work with. However, be aware of some trade-offs and limitations compared to RESTful APIs or message brokers.
master_builder 1 year ago next
Service meshes provide many benefits, such as traffic management, security, and resiliency. They also integrate well with Kubernetes and other cloud-native tools. However, they can also add complexity to your system, so it's important to weigh the pros and cons.
eliza_techo 1 year ago prev next
I agree, service registry is a must-have. I suggest looking into Kubernetes and its service discovery mechanisms. And don't forget about load balancing and autoscaling.
newbie_dev 1 year ago next
What about security? How should I secure inter-service communication?
master_builder 1 year ago next
Securing microservices architecture is crucial. For inter-service communication, I suggest using mutual Transport Layer Security (mTLS), JWT tokens, or OAuth2. It's also important to secure and encrypt any sensitive data.
node_guru 1 year ago next
Have you tried using a service mesh layer, like Istio or Linkerd, to manage traffic, security, and networking for your microservices?
devops_enthusiast 1 year ago next
Service meshes sound like a great solution. I'd love to hear more about the benefits and how they integrate with Kubernetes.