3 ms·
I've been programming in elixir for 5 years now. Currently on my 3rd year as CTO of a startup. I chose elixir for the greenfield project because we wanted real
by cultofmetatron 5y ago
I've been programming in elixir for 5 years now.
Currently on my 3rd year as CTO of a startup.
I chose elixir for the greenfield project because we wanted realtime sync for all devices and
the smaller projects I worked on before in elixir went off without a hitch.
I also found its concurrenly handling and performance far superior to node and I was producting far less bugs due to its functional nature.
3 years in and I'm very satisfied. There are a few epics we took on that would have been much more expensive to do in go or node.
For example, we made a partnership with a credit card device terminal. Their interface required one persistent webocket connection per restaurant.
IN another language, I would have had to coordinate with my devops guy to have a dynamic system to allocate a process for each of our accounts and route that to our devices.
The intended use case were on premise POSes so our cloud based solution wasn't somethign they had planned on supporting.
Anyways, I was able to configure horde and a dynamic registry to boot up a process for each active account and automatically resserect on crash. Since pubsub is built in,
It was easy to pass along data from it to all the devices over the channels interface. Best part is it was all doable within the code base running without any changes to out deployment.
Overall, I've been happy with elixir. the only bg downside is its gotten a bit boring. Things just work which leaves me spending time on rust in my free time when I want a challenge.