7 ms·

You're right. However, a lot of new (or just bad) devs miss the whole Keep It Simple Stupid concept and think that they NEED Kubernetes-shaped solutions in ord

You're right. However, a lot of new (or just bad) devs miss the whole Keep It Simple Stupid concept and think that they NEED Kubernetes-shaped solutions in order to "do it the right way". Many times three web servers and a load balancer are exactly what you need.

threeseed 7y ago
And then what about when you need to add monitoring, logging, APM, tracing, application metrics etc. Suddenly you have gone from 3 instances to 20.
- bdibs 7y ago
  I personally went from 4 servers to 5, self hosting ELK and it works great.
- mmazing 7y ago
  Adding an entirely new instance is not the only way to accomplish each of those things. A lot of those things can be treated just like applications. You don't need a whole new computer to run Outlook, another computer to run Sublime Text, another computer to run Chrome, etc etc. All of that is irrelevant to my main point though. It's never one size fits all and then all your problems are solved. You are far better off actually assessing your needs and picking the right solution instead of relying on solutions that "worked for bigger companies so they'll work for me" without really giving it a lot of thought if you need to go that far.
  - threeseed 7y ago
    Almost all of those aren't single binaries like Chrome. They often have their own databases, search engines, services etc to deploy along with it. And necessitate multiple instances for scalability and redundancy.
    - jbergens 7y ago
      They can be shared across a company. Office one team handels those all other teams can just use them.
  - rumanator 7y ago
    > Adding an entirely new instance is not the only way to accomplish each of those things. A lot of those things can be treated just like applications. That's what containers are. Containers are applications, packaged to be easily deployable and ran as contained processes. That's it. Kubernetes is just a tool to run containers in a cluster of COTS hardware/VMs. I've said it once and will say it again: the testament of Kubernetes is simplify so much the problem of deploying and managing applications in clusters of heterogeneous hardware communicating through software-defined networks thay it enable clueless people to form mental models of how the system operates that are so simple that they actually believe the problem is trivial to solve.
    - mmazing 7y ago
      Again .... that might be the best solution for your company, or it might be introducing complexity where it's not actually needed. It all depends on the situation and needs of whatever problem you are trying to solve.
- aganame 7y ago
  Aren't those rather trivial to do if you didn't make the mistake of choosing a microservice architecture?
yahyaheee 7y ago
I get the point but I’ve also seen three web servers and a load balancer go terribly wrong at a number of places as well. L8s provides a lot of portability that you would need a disciplined and experienced engineer to match with raw deployments.
raghava 7y ago
> Many times three web servers and a load balancer are exactly what you need. May be, just may be, they want k8s not to create value but to develop/enrich resumes - in order to signal that they are smart and can do complex stuff.

threeseed 7y ago

And then what about when you need to add monitoring, logging, APM, tracing, application metrics etc. Suddenly you have gone from 3 instances to 20.

bdibs 7y ago
I personally went from 4 servers to 5, self hosting ELK and it works great.
mmazing 7y ago
Adding an entirely new instance is not the only way to accomplish each of those things. A lot of those things can be treated just like applications. You don't need a whole new computer to run Outlook, another computer to run Sublime Text, another computer to run Chrome, etc etc. All of that is irrelevant to my main point though. It's never one size fits all and then all your problems are solved. You are far better off actually assessing your needs and picking the right solution instead of relying on solutions that "worked for bigger companies so they'll work for me" without really giving it a lot of thought if you need to go that far.
- threeseed 7y ago
  Almost all of those aren't single binaries like Chrome. They often have their own databases, search engines, services etc to deploy along with it. And necessitate multiple instances for scalability and redundancy.
  - jbergens 7y ago
    They can be shared across a company. Office one team handels those all other teams can just use them.
- rumanator 7y ago
  > Adding an entirely new instance is not the only way to accomplish each of those things. A lot of those things can be treated just like applications. That's what containers are. Containers are applications, packaged to be easily deployable and ran as contained processes. That's it. Kubernetes is just a tool to run containers in a cluster of COTS hardware/VMs. I've said it once and will say it again: the testament of Kubernetes is simplify so much the problem of deploying and managing applications in clusters of heterogeneous hardware communicating through software-defined networks thay it enable clueless people to form mental models of how the system operates that are so simple that they actually believe the problem is trivial to solve.
  - mmazing 7y ago
    Again .... that might be the best solution for your company, or it might be introducing complexity where it's not actually needed. It all depends on the situation and needs of whatever problem you are trying to solve.
aganame 7y ago
Aren't those rather trivial to do if you didn't make the mistake of choosing a microservice architecture?

yahyaheee 7y ago

I get the point but I’ve also seen three web servers and a load balancer go terribly wrong at a number of places as well. L8s provides a lot of portability that you would need a disciplined and experienced engineer to match with raw deployments.

raghava 7y ago

> Many times three web servers and a load balancer are exactly what you need. May be, just may be, they want k8s not to create value but to develop/enrich resumes - in order to signal that they are smart and can do complex stuff.