VGT?

We run a large distributed cluster (currently 4 DCs spanning the US) and use hot code reload for live patches when needed and rolling deployments for our standard releases.

To add to this topic, people who do not know about erlang's hot code loading should watch this talk : https://www.youtube.com/watch?v=pQ0CvjAJXz4

A multi-DC running cluster where parts are progressively swapped at runtime. No database, only OTP.

I think that's a good point. Our largest pain point with Elixir is definitely the size of the community and the associated dearth of niche libraries. The technology behind it, though, is solid enough that once those libraries exist, things really take off. My team wrote several open source medical libraries for Elixir and we've seen it really expand into the healthcare market.

I'd like to have a look at those, have a github link?

Yes! Thanks for the interest, hope they're helpful!

for HL7: https://hexdocs.pm/elixir_hl7/main.html

for MLLP: https://hexdocs.pm/mllp/readme.html

i am still fine in my used 2012 12k prius.

see the novel kiln people and the transparent society essays by David Brin

good god, i would quit in a heartbeat.

Santa Clause was also my complete religious breaking point as a child!

Is there a video of this ui??

Here's one of our public traces if you want to try the real thing: https://v3.dagger.cloud/dagger/traces/6898273d59ad62a6df1e9e...

I think some of it is shown on this page:

https://docs.dagger.io/features/visualization/

We use something like this at scale, similar to Riak's design. We use it to store things like the active state of millions of hospital patients in RAM for high availability (zero downtime when DCs or nodes fail). One copy per data center with a writer at one of the DCs. Our current cluster has 32 nodes (8 per DC -- we should have 5 DCs across the US but only have 4 at the moment). You can learn more about it here: https://www.youtube.com/watch?v=pQ0CvjAJXz4.

I used to do this kind of work as a contractor (for logistics and manufacturing), and I've it seen go both perfectly well and tragically wrong. The most common points of failure I've seen are underestimating the amount of business/domain knowledge needed and picking the wrong team.

Sometimes it's worth bringing someone in to build a temporary prototype to test the waters (I once wrote a wireless hand scanner pick system for a startup warehouse in a weekend -- they planned to throw my code away but just needed something functional right then.)

I would only pursue it if:

- your business is truly niche/unique and there's a significant cost due to process friction

- the total amount of work needed to have a functional product could be completed by one or two good developers in a matter of weeks/months.

If you do pursue it, I would try to take advantage of the Python Paradox (https://paulgraham.com/pypar.html) and hire someone, counterintuitively, working in a niche technology. You could probably find someone pretty good willing to build it in Elixir without much trouble.

> You could probably find someone pretty good willing to build it in Elixir without much trouble.

While I agree with that assessment, you’ll also spend the rest of your days cursing yourself if they were to leave.

It's not hard to learn and my current Fortune 100 has had zero trouble hiring for it.