3 ms·
Docker is messy, containerization is full of s##t and bugs. But I'll take the gamble. The world moving toward standardization is a BIG deal. Docker doesn't add
by csomar 9y ago
Docker is messy, containerization is full of s##t and bugs. But I'll take the gamble.
The world moving toward standardization is a BIG deal. Docker doesn't add complexity. Docker reveals the real complexity of the problem when you require a stable solution.
Let's take this simple example. Let's say you setup shop with a Virtual Server that has Ubuntu xx.xx and you write a simple PHP code that sends an email:
mail( poor@soul.com, "spam" );
It works. It works fine not because it is simple, but because it hides the complexity.
-> It is not clear what it sending the email here.
-> It is not clear what PHP is using to send the email.
-> It is not clear how your Virtual Server is relying the email.
-> It is not clear what will happen if it fails.
-> It is not easy to change after you have coded it.
That single line is very simple and works. But it is a mess as you keep progressing. The reason I keep investing in Docker is this: I have been burned to the core by complexity that just start pooping out on my face as my day moves.
Imagine you have this line of code instead:
mail_service->send( poor@soul.com, "Still spamming" );
You have the following:
-> Consul managing your nodes.
-> Mail nodes that expose a mail_service
-> The Mail service needs configuration. Tricky. Can setup and configure an SMTP server, load up and build some template docker file made by some other guy, or pull the MailChimp docker container and give it my API keys.
-> Maybe I'll have three instances. Prioritize the most efficient one and leave the others just in case.
-> Mailchimp goes down? Consul moves traffic to my other nodes.
-> Mail failure? Report to my logging node. Maybe we need to standardize this. So I just load my mail node that integrates with my logging node.
-> Moving from MailChimp to MailXYZ doesn't require any code modifications. No updates for the code. No downtime.
So does it work now? Uh, tough call. Yes, it is a gamble. It is a big gamble. But it is a big gamble that will make us all better off. So let's invest in it. Remember that the tech sector was mostly made out of technological gambles.
TL;DR: Docker is messy. But not because Docker or containerization sucks. It is because they expose the messiness of the real world. Your development WAMP hides a ton of this complexity that only reveals itself once you start scaling and going through practical tests.