There are actually many ways you can manage persistent storage on docker. If you are just planning on deploying to AWS EC2 you should be able to use persistent volumes off the bat (don’t use ephemeral storage when you spin up your instance). And if you are looking at ECS and docker, you can mount your EC2 directories onto your docker containers easily.
minhajuddin
mkunikow
You need storage as a service EBS vs S3 vs EFS: When You Need Which AWS Storage Option?,
About blockchain AWS also lately added blockchain support Web3 on AWS - Amazon Web Services managed-blockchain .
0
rodmclaughlin
dimitarvp
An open-source library that does automatic servers provision to AWS, given a minimal configuration file. It will make the book more valuable and will give you additional exposure and respect.
2
bjunc
I’d definitely be interested in this, particularly regarding the layer of Docker and CI. We’re using Docker containers on AWS for everything but Elixir, actually. For Elixir, we’re pushing to Heroku (the nightly reset doesn’t impact us). I think the key is simplicity. I shy away from complex / multi-dependency / fragile devops setups.
1
mkunikow
dimitarvp
jfrolich
jfrolich
Actually I think what is lacking at this point is a good approach that works for 95% of the people, so everyone has to reinvent the wheel.
A good multi-stage docker image would help that builds a phoenix application to docker with good defaults (I have a good one, looking to open source).
From then it will be general ECS as everything applies similarly to every docker image (whether it is python, ruby or elixir).
The Elixir specific part then is making distributed Erlang work. Part of this should be included in the docker image. Another part is the mechanics setting this up with ECS (VPC configuration, setting up service discovery).
Definitely interested to buy you book. I wish it would be available now 
1
minhajuddin
With AWS Fargate, if you end up using cumulative resources of 2vCPU/16GB for a month, you end up with:
2 (vCPU) x 0.0506 (vCPU cost per hour) x 720 (hours in a month) = $72.8640
16 (GB) x 0.0127 (GB cost per hour) x 720 (hours in a month) = $146.3040
--
Total: 219.1680
An on demand instance for the same configuration (r4.large) would cost you $95.760 which
would go down further if you use Reserved Instances (a 1 year no upfront RI would cost you $61.32).
So, if you have a service that needs to be up all the time, I’d just spin up a cluster and use ECS without Fargate. However, if you need containers for one off tasks which don’t need to run continuously I think Fargate is perfectly suited for that.
2