DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

Cover image for Forbes: It's The End Of Infrastructure-As-A-Service As We Know It: Here's What's Next
manish srivastava
manish srivastava

Posted on • Updated on

Forbes: It's The End Of Infrastructure-As-A-Service As We Know It: Here's What's Next

Hello, friends. I am sharing an article published on forbes.com by Mr Tolga Tarhan,Forbes Councils Member. I am quoting an excerpt from this article and you can read further by clicking link at end of this article.

A decade ago, running virtual machines (VMs) in the cloud was state-of-the-art. It made cloud migration relatively simple: Companies could just shift the VMs they were already running on their on-premises servers to the servers of an infrastructure-as-a-service (IaaS) vendor. Freed from the burden of physical server maintenance, companies gained flexibility and cut costs.

But today, no one is building new applications based on VMs. Instead, they're turning to two models that are more cost-effective, low-maintenance and scalable than VMs can ever hope to be: containerization and serverless computing. These two models, not VMs, represent the future of compute.

Read more here... Forbes

Remember Cloud Brother Story? ( Part -1,Part-2 , Part -3
So, What is your opinion.

Must Read: Please refer to my previous posts regarding creating your cloud service like the digital ocean or google cloud. Part 1 and Part-2 and Part-3

Top comments (7)

Collapse
 
ben profile image
Ben Halpern

Yeah I'd say that this is probably true.

Most companies should really care about the ABCs of their application logic and try and operate in an environment where they care less about the infrastructure.

I'd say the caveat is that nobody should be writing their software on anything that's so novel or experimental that they might need to upend it when tastes change. And nobody should be writing on anything so proprietary they can't be flexible when needs change.

Collapse
 
brandinchiu profile image
Brandin Chiu

In this industry, If you stop moving, you die.

Five years from now we'll be talking about why containerization was a silly concept and this next new thing is going to the go-to moving forward.

Collapse
 
ben profile image
Ben Halpern

On the other hand, we've made a lot of progress with a plain old Ruby on Rails app deploying on Heroku.

We're evolving a little now, but even our evolution isn't to the latest and greatest, it's just to whatever solves our problems. There's something to be said about not getting too caught up in the hype.

Collapse
 
brandinchiu profile image
Brandin Chiu

I'm discussing more as an idea of the industry as a whole as opposed to specific projects :)

Collapse
 
aronjohnson profile image
Aron Johnson

The abstraction layer that we concern ourselves with should absolutely continue to shift up the stack (physical > VM > container > function) as those lower layers are commoditized.

With that said, the tone of the Forbes article is a bit dramatic. Technology stacks often have a long tail. Will there be an end to IaaS? Sure. Is it near? Likely not.

Absolutely use containers and serverless where it makes sense. Sometimes though, you just need to ship some software, and good old IaaS does the trick.

Collapse
 
spiritupbro profile image
spiritupbro

love the insigt fosho serverless is the future

Collapse
 
jwp profile image
John Peters

Yes VMWare is toast.

Timeless DEV post...

How to write a kickass README

Arguably the single most important piece of documentation for any open source project is the README. A good README not only informs people what the project does and who it is for but also how they use and contribute to it.

If you write a README without sufficient explanation of what your project does or how people can use it then it pretty much defeats the purpose of being open source as other developers are less likely to engage with or contribute towards it.