One would hope that the future of computing is driven by something other than vendor generated hype and desire to obscure the true cost of service by pushing nebulous concepts 
. “Serverless” existed for a long long time it’s called shared hosting
andre1sk
1
mkunikow
Ok near future are containers. The further feature will be “serverless” architecture, preferred term is even driven or lamda architecture.
0
adammokan
I don’t have any personal beef with Docker, but for all of my Elixir work in production - which fits into a bigger ecosystem of other languages - I’ve fully embraced releases so that I’m just distributing a tar file to servers. No need to install Elixir/Erlang. It’s all self-contained and deployment just entails replacing the unpacked directory with a new version.
Aside from early frustration of figuring out how to do a release correctly with my projects, it has been perfect from a development and devops perspective. I’m pretty sure the only thing I do now for a production Elixir node is run an ansible script to configure the firewall rules and I’m ready to deploy to it.
But, as others mentioned, I know Docker can be helpful on the dev side of things - especially if you need a build server for releases and don’t have access to physical hardware or politics prevent you from using an AWS isntance or something.
3
andre1sk
Would you consider writing a short post on how you handle releases? I think a lot of people would really appreciate it as it’s seems to be the topic that often comes up.
2
adammokan
pancake
Sure. For about 4-5 years now, my stack looks like this:
- CI: Codeship/MrJenkins
- Automation: fabric (http://www.fabfile.org/) with aws-cli or AWS CodeDeploy
Right now I use AWS for all projects.
edit: I forgot to mention that I’m working mostly with python projects, but Elixir projects fit this stack too
1