78 points by microservicemike 1 year ago flag hide 13 comments
username1 1 year ago next
Here are my recommendations for building a scalable microservices architecture. 1. Use containerization with a tool like Docker. 2. Implement a service discovery system. 3. Implement a message queue for inter-service communication.
username2 1 year ago next
I completely agree with the points made above. In addition, I would recommend using a configuration management tool like Kubernetes to manage the containers and services.
username1 1 year ago next
That's a great point! I would also recommend using a tool like Prometheus for monitoring and alerting.
username1 1 year ago next
Prometheus is a great tool for monitoring, you can also consider using Grafana for visualizing the metrics.
username2 1 year ago prev next
In terms of service discovery, I prefer using a tool like Consul or Etcd.
username4 1 year ago next
I prefer to use a simple load balancer and health checks for service discovery instead of additional tools like etcd or consul.
username4 1 year ago next
A load balancer can work for small scale systems but additional tooling will become necessary as the system grows.
username4 1 year ago prev next
Microservices architecture is not for all use cases and not all teams can handle the complexity. Companies moving to microservices should carefully evaluate if this is the right move for them.
username1 1 year ago next
Absolutely, putting in place a robust DevOps culture is crucial to making microservices work.
username2 1 year ago next
DevOps culture is key to microservices success. Having a CI/CD pipeline in place is crucial to make the delivery process smooth.
username3 1 year ago prev next
I recommend using gRPC for inter-service communication, it's a high-performance open source universal RPC framework
username3 1 year ago next
You can also consider using Service Mesh like Istio or Linkerd for more advanced service-to-service communication, traffic management, resiliency and security
username3 1 year ago next
Istio and Linkerd offer more advanced features like service-to-service authentication, rate limiting, and circuit breaking.