5 ms·

Is there a hello world version of this? I have been trying to pick up IaaS (insanity as a service) and it has been really difficult. At what point does it make

Is there a hello world version of this? I have been trying to pick up IaaS (insanity as a service) and it has been really difficult. At what point does it make sense to use docker? Is it worth learning all of the above crazyness if you have less than 10K people using your service and are 1 person?

dkarapetyan 11y ago
No, it's all just terrible software managed by even more terrible software. It's all very aesthetically unpleasant and when I look for good software I look for a certain "coherence" that I have not found in any of the cloud providers. If you do things right and stage your artifacting and deployment process properly then that is 90% of the battle I think because none of the cloud providers are magic. Any service they have that promises to abstract away your deployment and configuration pipeline is a bold-faced lie. Heck, they don't even have a way for automating the network topology configuration that isn't a nightmarish maze of JSON (I'm speaking of course of cloud formation). So even if you are using docker, that is in no way a solution to a proper deployment pipeline with properly versioned artifacts and dependencies.
- vonklaus 11y ago
  so just to be clear, you are a huge fan of bundled cloud services then? can't really praise them enough? Cheers, will stick with getting better at developing software and not worry about the container craze yet. thanks.
  - dkarapetyan 11y ago
    Ya, there is no substitute for fundamentals. If you don't have that down then docker is not gonna help. Like C++ it just makes it easier to shoot yourself in the foot harder.
    - vinceguidry 11y ago
      Can't harp on fundamentals enough. The thing to realize is that everything you do in an automated fashion can also be done manually. If you haven't worked out how to do it manually, then when your automated solution fails to work, it's going to be much easier to troubleshoot if you know the basics. Hence why I prefer things like OOCSS over Bootstrap, Capistrano over Docker. Bootstrap forces your markup to conform to your framework, drowning you in incoherent class names that are going to flee your mind the second you have to remember why you put them there. OOCSS makes you treat your markup and CSS holistically, so that when it comes time to troubleshoot a browser bug, you can easily apprehend what your markup was supposed to do and why you did it that way. Docker automates things that don't really need to be automated, unless you've got the kind of problem that really could make use of Docker's abstractions. People think they need Docker when they don't, then get surprised when Docker doesn't magically solve the problem they were hoping it would solve. Make things work in the simple case, and then iterate towards the complex. If you ignore this, then you will eventually find yourself in the situation where you have a deadline to meet that you simply won't be able to meet because you're writing technical checks that your skills won't be able to cash.

dkarapetyan 11y ago

No, it's all just terrible software managed by even more terrible software. It's all very aesthetically unpleasant and when I look for good software I look for a certain "coherence" that I have not found in any of the cloud providers. If you do things right and stage your artifacting and deployment process properly then that is 90% of the battle I think because none of the cloud providers are magic. Any service they have that promises to abstract away your deployment and configuration pipeline is a bold-faced lie. Heck, they don't even have a way for automating the network topology configuration that isn't a nightmarish maze of JSON (I'm speaking of course of cloud formation). So even if you are using docker, that is in no way a solution to a proper deployment pipeline with properly versioned artifacts and dependencies.

vonklaus 11y ago
so just to be clear, you are a huge fan of bundled cloud services then? can't really praise them enough? Cheers, will stick with getting better at developing software and not worry about the container craze yet. thanks.
- dkarapetyan 11y ago
  Ya, there is no substitute for fundamentals. If you don't have that down then docker is not gonna help. Like C++ it just makes it easier to shoot yourself in the foot harder.
  - vinceguidry 11y ago
    Can't harp on fundamentals enough. The thing to realize is that everything you do in an automated fashion can also be done manually. If you haven't worked out how to do it manually, then when your automated solution fails to work, it's going to be much easier to troubleshoot if you know the basics. Hence why I prefer things like OOCSS over Bootstrap, Capistrano over Docker. Bootstrap forces your markup to conform to your framework, drowning you in incoherent class names that are going to flee your mind the second you have to remember why you put them there. OOCSS makes you treat your markup and CSS holistically, so that when it comes time to troubleshoot a browser bug, you can easily apprehend what your markup was supposed to do and why you did it that way. Docker automates things that don't really need to be automated, unless you've got the kind of problem that really could make use of Docker's abstractions. People think they need Docker when they don't, then get surprised when Docker doesn't magically solve the problem they were hoping it would solve. Make things work in the simple case, and then iterate towards the complex. If you ignore this, then you will eventually find yourself in the situation where you have a deadline to meet that you simply won't be able to meet because you're writing technical checks that your skills won't be able to cash.