4 ms·
I've seen more than once recently an engineer saying that software solutions outside of the Serverless ecosystem (FaaS, DB, etc) is "the new legacy". And that c
by haolez 4y ago
I've seen more than once recently an engineer saying that software solutions outside of the Serverless ecosystem (FaaS, DB, etc) is "the new legacy". And that cloud providers have solved all the pains that Erlang was supposed to address.
What's your feeling on this? Elixir sounds very compelling to me, but I worry that I might be going in a direction that's not where the industry is going.
- davydog187 4y agoServerless? You mean vendor lock-in, distribution issues and reproducibility issues, etc?
- haolez 4y agoYeah. There are obvious downsides, but what if your competitor.manages to outperform you with such tools? That's my concern
- conradfr 4y agoOutperform in which aspect?
- haolez 4y agoDeliver more features, faster.
- davydog187 4y agoYour competitor beat you while you were rewriting your product to be serverless
- rawoke083600 4y agoHaha :D Too True !
- nix23 4y ago>engineer saying that software solutions outside of the Serverless ecosystem (FaaS, DB, etc) is "the new legacy" It's complete blindness to the reality. Trusting one single provider for your whole service (often not even completely opensource) is the same trap as Windows or Oracle in the 90's...just worse (because not on prem)...but hey history repeats itself ;)
- bo0tzz 4y ago> cloud providers have solved all the pains that Erlang was supposed to address. Assuming this is talking about tools like Kubernetes, they operate on a different level. The OTP's failure tolerance model operates on a (relatively) very small scale inside your application, whereas Kube operates on a whole-application level. Rather than obsoleting OTP, Kubernetes actually complements it.