91–100 of 176 posts
A new programming language which hides the fact that your code is running across multiple machines from you. Similar to OOP, you'll define some level of structure and the compiler will figure out how to best distribute it across the resources given to it.
Something much, much, simpler. I'm not convinced that /for most companies/ k8s adds enough value when compared to all the added complexity (not to mention the yaml soup!).
Working for a small startup that uses both k8s and more traditional infrastructure, I've found the yaml soup that comprises a reliable k8s system is not much worse than the yaml/hcl soup of our ansible/terraform provisioning scripts.
Something much, much, simpler. I'm not convinced that /for most companies/ k8s adds enough value when compared to all the added complexity (not to mention the yaml soup!).
Working for a small startup that uses both k8s and more traditional infrastructure, I've found the yaml soup that comprises a reliable k8s system is not much worse than the yaml/hcl soup of our ansible/terraform provisioning scripts.
That will come, but it’s a ways out and difficult to see. Most of what we’ll see are different abstractions that will utilize linux under the hood. Same with kubernetes. It’s not that a new kind of OpenStack is going to usurp it, it’s that what comes next will be built on top of it as it becomes mroe and more the norm… until the next major computing revolution. (completely decentralized storage on phones a la pied piper? quantum computing?)
As businesses start to realize microservices aren't really worth it due to the complexity and cost it entails, they will start reverting back to hosting monoliths on VMs or services like Heroku/Netlify/Laravel Forge/Beanstalk, and they'll find out they can save a lot of money on compute and man hours by doing this. For more simple workflows, e.g. a single API endpoint, there's serverless and other SaaS services out t…
I think the pendulum has swung a bit too far from its optimum with serverless and microservices. The main issue I have with both is the huge complexity and friction between how it runs on a developer machine vs how it runs in production. For me the sweet spot is monolith(-ish) 12-factor applications packaged up in containers. In this setup I can just `docker-compose up` my dependencies (postgres, redis, rabbitmq, oth…
exactly this.
Once you go with this you take technology out of a microservices definition and all that remains is how you scope your service.....
Kubernetes automates and standardizes some of the best practices around building reliable systems in a platform agnostic way. We never got there with VMs: Amazon ec2 instances are not the same as GCE instances are not the same as VMware VMs but a kubernetes api is the same everywhere (and providers are incentivized to standardize their offerings). Whatever comes next would have to be something that can standardize ev…
> We never got there with VMs: Amazon ec2 instances are not the same as GCE instances are not the same as VMware VMs This is true but is that such a huge deal? We successfully moved from AWS to GCP and it wasn't a massive deal; just different terminology for the same concepts.
Compare that to redeploying your k8s manifests from an EKS cluster to a GKE cluster or vice versa. Its definitely not fully platform agnostic, but it requires much less engineering effort.
As businesses start to realize microservices aren't really worth it due to the complexity and cost it entails, they will start reverting back to hosting monoliths on VMs or services like Heroku/Netlify/Laravel Forge/Beanstalk, and they'll find out they can save a lot of money on compute and man hours by doing this. For more simple workflows, e.g. a single API endpoint, there's serverless and other SaaS services out t…
Docker with k8s is awful when it comes to resource metering. Docker is terrible with security and resource isolation. K8s, in general, is awful IMO because of the way it was architected and implemented.
Xen-ified "containers" (regular VMs but managed) with an ability to inject uniform, templated, configured concerns is how to do services: micro or macro; ephemeral app, infrastructure, or backend. Also, backups and logs have to live somewhere else.
Basically, a APPaaS/PaaS/IaaS in the spirit of K8s + OpenStack but much cleaner, workable, easier, simpler, fewer choices, more usable, more reliable, less stupid, and more standardized. (Discovery is insecure and fundamentally unworkable; top-down provisioning knows exactly what exists and is alive so use that as the authoritative single-source-of-truth.)
There is no other way I can see.
As businesses start to realize microservices aren't really worth it due to the complexity and cost it entails, they will start reverting back to hosting monoliths on VMs or services like Heroku/Netlify/Laravel Forge/Beanstalk, and they'll find out they can save a lot of money on compute and man hours by doing this. For more simple workflows, e.g. a single API endpoint, there's serverless and other SaaS services out t…
The Herokus of the future will run on top of kubernetes.