News for hackers. Stuff that matters.
Re:Maybe You Don't Need Kubernetes by AaronM on Friday March 22, 2019 @07:18PM (#19467853)
If your application is 50 microservices, how would you manage that on ec2 instances?
Re:Maybe You Don't Need Kubernetes by colechristensen on Friday March 22, 2019 @08:10PM (#19468120)
One autoscaling group, AMI, instance (or more than one) per service.
Re:Maybe You Don't Need Kubernetes by Karunamon on Friday March 22, 2019 @09:15PM (#19468424)
A nontrivial portion of those microservices could probably run on Lambda.
Re:Maybe You Don't Need Kubernetes by DanielBMarkham on Friday March 22, 2019 @07:23PM (#19467878)
Why does the number of microservices have anything to do with where they might live? Wouldn't that be much more related to CPU load?
Re:Maybe You Don't Need Kubernetes by SteveNuts on Friday March 22, 2019 @07:26PM (#19467897)
Because you generally want to deploy them independently. If you have 50 microservices and have to run an AMI build every time that's going to significantly slow you down. With containers you generally only deploy the service that has changes to a VM that doesn't change as often.
Re:Maybe You Don't Need Kubernetes by DanielBMarkham on Saturday March 23, 2019 @08:06AM (#19470104)
You want them to be independent, atomic. How they are deployed and the choice of technology you choose to couple them with? That should be driven by load -- and dynamic.

The reason everybody's so hot on microservices to begin with is that we kept coupling everything all together and it became a huge mess to manage. You don't want to repeat that mistake, only at cloud scale.