re: Containers vs. Serverless from a DevOps standpoint VIEW POST

VIEW FULL DISCUSSION

Nice article. Except for the cost analysis.

Serverless, in the long run, will cost you more, no matter the cloud provider. There are a few reasons for this.

Fast time-to-market often means suboptimal code and we are paying for pure cpu cycles.
All the niceties, autoscaling, built-in monitoring, etc, that come with serverless cost money, so that adds to the price you pay for serverless.

A well-designed kubernetes cluster will beat serverless price-wise for same type of workloads.

I think you're missing the point I wanted to make.

We're not supposed to compare the two technologies point-for-point, but instead, use them where they excel in their own category. Please don't position yourself in the container tribe or serverless camp. Open your mind to the opportunity, and advantage, both can provide.

Based on your use-case, user traffic, and throughput intensity, both can be the better choice. It's up to you to make that choice.

A much smarter man than me once said:

"Build serverless first. If needed move to containers."
--Adrian Cockcroft (@adrianco) at ServerlessConf

I trust his judgment. 😊

Thanks for reading, I hope you stick around and read one of my next articles. Cheers!

Exactly. E.g. In IoT doing Machine Learning at the Edge (as in Edge Computing) oftentimes Kubernetes or containers in general aren't possible. Serverless is the only lightweight code that can actually run there. Of course increasingly powerful processors & boards are being developed so it may not be an issue to select either in a year from now.

code of conduct - report abuse