>But with container orchestrators, you get the ability to design a polyglot with more fluidity in your design. You are then adding some redis/memcached, kafka

>But with container orchestrators, you get the ability to design a polyglot with more fluidity in your design. You are then adding some redis/memcached, kafka or something similar, etcd perhaps and kubernetes. A bunch of technologies your developers need to use properly and be running to develop on. As opposed to having an easy to use single technology named Erlang which is almost certainly good enough for your needs. And your developers can easily be running a distributed system of erlang nodes locally without any issues or complex setups.