4 ms·

Don’t use Kubernetes or Microservices. Solves most problems. Not even being sarcastic.

• rumanator 7y ago
  In your opinion what's wrong with Kubernetes or microservices?
  • quickthrower2 7y ago
    Not the OP, but I'd say use only Kubernetes if you have the time to dedicate for the team to learn that technology and it's mental model.
    • pbar 7y ago
      From a developer point of view, one should not have a mental model in play for Kubernetes, the standard 12 factor pattern should be it. If not, the infrastructure and the app are strongly coupled
    • rumanator 7y ago
      The overall mental model is not rocket science, and managed Kubernetes services remove most of the barriers to entry. In fact, most of kubernetes' mental model is in fact a direct reference of basic requirements to run containers on any platform.
• ellius 7y ago
  In general I think matching your tools to your needs, and coming up with solutions that are as simple as possible (but not simpler) is a super power and hard to get right. Your goal should always be to maximize your leverage by hiding and offloading as much complexity as you can while still meeting your requirements.
• gitgud 7y ago
  Microservices... Instead of 1 server you have N servers to maintain and scale.... "premature optimization is the root of all evil" - Donald Knuth
• oftenwrong 7y ago
  A monolith is simpler than a bunch of services. If you can run your system as a monolith, you should.