I was about to write exactly the same response than j ;-)
My own point of view: A good combo of Docker + local stuff (because sometimes it's just more convenient/fast).
My own point of view:
it's important to known the available options, and their pros'n cons (ie a docker-hosted database versus a local one... people might have different needs, so the tradeoffs might be different from one person to the other one)
therefore it's not a one-size-fits-all question. And not even a 100% vagrant vs 100% docker vs 100%local question.
Best advice I could give to a friend looking into this:
start with the tool you know the best
when you have time, try to ramp-up with another one to learn to replace your solution. Talk about what looks better, what looks worse, and what you struggle to do, in order to let me help you fix the details as you learn
as you gain mastery in that other tool, re-evaluate which one could be the most helpful/useful for your own workflow and needs
In my case is just a simple test environment but vagrant can be nice for this stuffs...
yes :) idd I have various setups running. and if the complexity increases or the amount of parallel projects increases to me a virtualization seams to be the right choice.
I lean towards docker but rkt or vagrant are good too.
And if I really wanna unify all behaviours a complete hybrid virtualization can save a lot of trouble in an heterogeneous setup (apple devs, linux devs, windows devs)
but if i have the choice I stick to containers .... anyhow :) .... as I mentioned it depends
Sébastien Portebois
Software architect at Ubisoft
I was about to write exactly the same response than j ;-)
My own point of view: A good combo of Docker + local stuff (because sometimes it's just more convenient/fast).
My own point of view:
Best advice I could give to a friend looking into this: