The DevOps industry has never been more exciting, with the almost constant advent of new technologies, tools and languages. But with so much choice, how can engineers today know what to work with?
One key instance of this is serverless and containers – both amazing technologies, and both of which provide productive, machine-agnostic abstractions for engineers to work with.
Breaking down the two can offer some insight into what the technologies can offer respectively. For instance, with serverless, you get the basic observability tools out of the box, whilst the container space has a more mature and diverse ecosystem of tools available. Serverless and container also differ on their vendor lock-ins, with the former having more risk of a lock-in than the latter.
Those that identify themselves as developers are more likely to prefer serverless, and those that identify as DevOps are more likely to go with containers.
When the distinction between serverless and container broken down, the conversation will be less about which technology should prevail, and more about which will help you to build the most effective products for your business.