Go for it 
it is actually aimed at programmers so you are the target market 
(It’s just that personally I am the sort of person who likes to read or learn as much about something as I can before jumping in 
)
As ODL commented, it will be fast from the get go - Phoenix response times are in microseconds 
Well that’s why I bought programming elixir, programming Phoenix and functional web development and been browsing the in the last month.
But the sad truth is until you write something you don’t know the language and the first few times you use it, you duck only after a few months of using a language you start to be mediocre (in my case) when using it
To see what a very simple Plug webservice looks like, here’s one of mine with only one endpoint that discovers how long people have followed a Twitch channel: Mikko Ahlroth / peliturbiini-followed-since · GitLab
Well, I think that I owe you an update here…
The project is now on the first stage unfortunately it started 2 weeks ago or maybe 3 and needs to be up and running in less than 2 weeks.
So I decided to stay with ruby and Sinatra, the good news is that 90% of this project is based on what I learned here and I think of it as the Elixir way(as I see it)
Basically what I’m doing is creating a Json based web services project that uses lots of threads that can always crash and send their state to another server if and when it happens.
I even have a gen server that is responsible of checking loads start and stop every other server, and of course is chosen with each restart.
So I basically wanted to say thanks, this community enriched me more than I could ever imagine, and I’m doing my best to use what I learned here, hopefully stage 2 would be Elixir but if not Elixir then my time here as a silent observer would be my inspiration.
We are not using Elixir in anger yet, but I think it would take a considerable effort to properly implement supervisors and gen_servers in ruby.
I should have said that my gen server is not going to be even 10% as smart as elixir more in the lines of removing computers from LB and adding them when they are up. (but the idea came directly fro it)
It would also be responsible of running test to make sure that every node is working as it should and every bot is doing what it is suppose to do.
The nodes themselves would be responsible of re-sending failed attempts to the Load Balance and letting the gen server know that they are down when it happens, which would initiate a replacement (shutting down the failed node or deciding the error was acceptable or not)
Well, I would give you one more update now and 2 more one when finished and another when I will finally move to Elixir.
From last week we are up, managed to do it within our 1 month time frame.
So what I have for now 12 computers each can do all the tasks I need.
State is decided by a transferable json, and when a request is failed it is retried and on second fail goes back to lb, second fail sends an error to queue and returns a success to my genserver.
Next stage I would fix 3 things:
