Holywow… My dedicated server is substantially better than those stats at ~$30/month… o.O
OvermindDL1
mkunikow
OvermindDL1
I have a few of these around, one in a california datacenter, one in canada, and one in germany, been pretty trivial thus far. As for scaling ‘on’ any given server, not needed to yet, not hit their limitations at this point, but upgrading them is pretty trivial and the SLA guarantees it within 15 minutes of putting in the request and payment without downtime except in some rare cases where a restart is needed (or the OS needs a reboot for it like when hotswapping the CPU).
0
ringods
I just signed up to be notified for your book publishment on LeanPub.
Regarding the content, since you are targeting Elixir and ECS, why not generalize that to Elixir and containers? AWS users will certainly look at EKS (Kubernetes) once they pass a certain infrastructure size.
With that perspective, I would very much like to know more on how a BEAM runtime behaves within a container. How to configure your container deployment (ECS/Fargate/Kubernetes) with regards to CPU and memory limitations. Are additional BEAM settings needed to have these limitations respected? E.g. in the Java world, you need to pass additional parameters when starting the JVM or it would calculate its heap size based on the amount of host memory rather than the container constraints.
Further on, how to debug CPU and memory bottlenecks for Elixir in a container runtime?
Second, once we go to Distributed Elixir, what are the gotchas regarding inter-container communication? How is the container network to be configured? Can it be easily integrated with a service mesh for secure inter-service communication?
Other stuff I’m interested in for Elixir & containers:
- Logging: how to configure the new Erlang logger and integrate it with e.g. log rotation & sidecar log shipper, CloudWatch Logs for structured logging, etc.
- Metrics: how to expose service level metrics and integrate that with, e.g. CloudWatch metrics.
- Message Queues
And you can select much more integrations which reside on the boundary between the Elixir runtime (BEAM) and cloud technology.
Ringo
3
tomciopp
minhajuddin
I had done a lot of writing on the book before the elixir release code was released and then a lot of things changed. I am planning to do a rewrite and release it by July of this year.
1
pillaiindu
I’m sorry if this sounds rude or stupid, but if I was deploying to AWS ECS, I won’t be using Elixir, in that case I’d be using Sinatra / Flask / some Go micro framework or Crystal language.
I’d love to read a book about how to deploy and scale Elixir (Phoenix) apps on a bare-metal network of servers or cheap VPSes.
0
ityonemo
Two things I’m interested in ecs wise:. 1) definitely pros/cons versus say using just bare AWS vms, and 2) how to set up (or not set up) pg2 clustering
0
minhajuddin
It doesn’t sound rude 
ECS provides a good deployment platform if you want to use containers on AWS. It has excellent support throughout the AWS stack. The benefits of the Erlang VM don’t go away when you use containers and containers are very convenient.
3
xpg
Elixir on AWS ECS definitely works very well.
I am somewhat puzzled by the way ECS and EC2 Auto Scaling groups work together. Scaling rules are set independently on the two, resulting in situations where ECS tries to start more tasks than can be run with the current cluster size. I’m not quite sure how scaling down works in the EC2 Auto Scaling group, either, as there is no obvious communication between ECS and EC2 Auto Scaling.
But I have a feeling that the ECS Capacity providers may improve the situation, but I haven’t had time to look into it yet.
Nevertheless, I am running a system in production with ECS and EC2 Auto Scaling. We go from 2 to 8 EC2 instances, depending on traffic to our system. Each EC2 instance runs a single task of our Elixir application. The application then figures out which nodes should run what services. This is really running smoothly.
Having said that, it would be really interesting to know of right and wrong ways to do things like this. There are thousand of ways to set something like this up. For instance ECS vs EKS
1