DEV Community

Discussion on: Docker everywhere is not a good thing.

Collapse
 
lexwebb profile image
Lex Webb

I think that data persistence is the real key here. Running web and service applications that store no data themselves are a real good candidate for containerising. But when it comes to permanent or critical data storage I think containerising is a bad idea.

In a world where the cloud is become the defacto way to go in terms of building modern and scalable solutions. Many cloud providers (AWS, Azure, Google) offer cloud native database solutions that have all of the scalability and security concerns taken care of out the box, with guaranteed uptime and data safety.

And with enterprise grade cloud solutions for source control and CI/CD being available for virtually no cost. Running Gitlab/Jenkins and other DevOps tooling yourself seems like a problem that we should not have to worry about any more.

As a developer, the thought of having to maintain a Kubernetes cluster is not something i want to have to concern myself with. As although Kubernetes and competing solutions are undoubtable powerful and very flexible, they are complex and expensive pieces of infrastructure to run vs a cloud native solution.

Of course to implement all of the above means that you have to belong to an organisation that is not afraid to utilise the cloud to its fullest extent. In my opinion, if it is good enough for massive corporations and governments, it's good enough for anyone.

Collapse
 
faraazahmad profile image
Syed Faraaz Ahmad • Edited

Those are really good points about data persistence. But couldn't you run a DB in another container and connect to that from your containerised app? I'm an undergrad so I don't know much about it, but I'd love to