Certainly there are solid points here, but he doesn't really address the ops side of the equation.
Certainly there are solid points here, but he doesn't really address the ops side of the equation. I wouldn't write a bunch of microservices on day 1 at a startup with no traffic. I have no doubt it is more complex than a monolith for development & operations. I have no doubt that it introduces a bunch of extra network related overhead.. But what happens when you have serious traffic? One of the main benefits of microservices is splitting the system up for deployment & provisioning. One particular part of the system might be very memory heavy, you can deploy it on a cluster of machines that are spec'ed appropriately. One part of the system might have a relatively constant workload so you can put it on dedicated hardware, while other parts might be cyclical and you can spin up and down instances to match traffic. You can deploy particular components independently which makes releases a much smaller affair. These things are not impossible with monoliths, but they are easier with microservices. So if the bigger pain point is deployment, scale, etc and not writing new code, then microservices might be a good choice.
Posted by krschultz on Aug 26, 2014, 7:45 PM
Tags
Related issues
- I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
- [BUG] No response from API error when Advisor is triggered
- I thought the general premise is that humans can't form social groups bigger than around ~200.
- great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
- > It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
- Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
reliability (Network)
I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
[BUG] No response from API error when Advisor is triggered
I thought the general premise is that humans can't form social groups bigger than around ~200.
great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
> It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Copy and paste not working
Full Offline Support
Certainly there are solid points here, but he doesn't really address the ops side of the equation.
Certainly there are solid points here, but he doesn't really address the ops side of the equation. I wouldn't write a bunch of microservices on day 1 at a startup with no traffic. I have no doubt it is more complex than a monolith for development & operations. I have no doubt that it introduces a bunch of extra network related overhead.. But what happens when you have serious traffic? One of the main benefits of microservices is splitting the system up for deployment & provisioning. One particular part of the system might be very memory heavy, you can deploy it on a cluster of machines that are spec'ed appropriately. One part of the system might have a relatively constant workload so you can put it on dedicated hardware, while other parts might be cyclical and you can spin up and down instances to match traffic. You can deploy particular components independently which makes releases a much smaller affair. These things are not impossible with monoliths, but they are easier with microservices. So if the bigger pain point is deployment, scale, etc and not writing new code, then microservices might be a good choice.
Comments (0)
No comments yet. Start the discussion.