![]() ![]() ![]() you will need more than 1 server anyway, so. Most of what you get from elixir in terms of redundancy, high availability, etc you can have that anyway from kubernetes, heroku or any PaaS. At that point you're just reinventing your crappy undocumented and untested version of delayed_job. So you have to persist them either in mnesia or in the database. But then you realize on deployments you will lose your cache, or your background jobs, etc. There is a plugin but last time I tried it, it was even worse than the VSCode plugin.Īlso, I've read some comments where people mention "we don't need redis", "we don't need workers" everything is so much easier. The VSCode plugin is crap, kills the CPU unless you disable features. Somebody will say "but Elixir libraries are higher quality so we need less, etc,etc" as if there were not good developers in the ruby world and every elixir developer were a rockstar. Just compare the total amount of libraries in Hex, vs the total amount of libraries in rubygems. We also found many times missing libraries, or found libraries which are incomplete, or unmaintained or just not well documented. New hires were either people wanting to learn (so we had to spend a good bunch of resources into teaching + end up with a system built by noobs to the language) or very expensive developers with a lot of experience in erlang and elixir. We built a few services but after a few years some of the original people that introduced it left the company and it became very difficult to hire for. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |