45 points by microservices_newbie 7 months ago flag hide 13 comments
johnsmith 7 months ago next
Great question! I'd recommend starting with a service registry, like Consul or etcd, and using containers with something like Kubernetes. This will give you a solid foundation for scalability.
janedoe 7 months ago next
I agree with johnsmith. Don't forget to consider the network layer and how your microservices will communicate with each other. gRPC is a good option for high-performance calls.
saramiller 7 months ago next
Consul and Kubernetes are both powerful tools, but they can also be complex to set up and manage. Be prepared to put in the time and effort to learn them.
jessrice 7 months ago next
Don't forget about data consistency! If your microservices share data, you'll need to think about how to keep it consistent across all instances. Consider using techniques like eventual consistency and Sagas.
lucymac 7 months ago next
Eventual consistency and Sagas are great ways to ensure data consistency, but they can be complex to implement. Make sure you understand the trade-offs and consider using a framework like Axon or Lagom to help simplify things.
andypeterson 7 months ago next
Implementing eventual consistency and Sagas can be complex, but they're worth it in the long run. Just make sure you understand the implications and plan for recovery scenarios in case something goes wrong.
davidlee 7 months ago next
Great point about recovery scenarios. You'll also want to make sure you have a good testing strategy in place to catch issues before they become production problems.
codemaster 7 months ago prev next
Also, don't forget about monitoring. You'll want to set up alerting and tracing with tools like Prometheus and Jaeger to quickly identify and fix issues as they arise.
brianpark 7 months ago next
Monitoring is key. I'd also recommend using load balancing and self-healing mechanisms to ensure high availability. Have you considered tools like Linkerd or Istio for this?
evankennedy 7 months ago next
Linkerd and Istio are both solid options for service mesh, but they can be heavyweight. If you're looking for something lighter weight, you might want to consider Consul Connect or NGINX Service Mesh.
alicejones 7 months ago next
Consul Connect is a good option, but it's still relatively new. If you're looking for something more mature, you might want to consider HashiCorp's Consul Service Mesh, which includes Consul Connect and other features like traffic management.
emilykim 7 months ago next
HashiCorp's Consul Service Mesh is a solid option, but keep in mind that it can be expensive if you have a large number of microservices. Make sure you understand the cost implications before you commit.
sophialeung 7 months ago next
Thanks for mentioning the cost implications. That's an important factor to consider when choosing a service mesh.