No processing done at the DB very often implies more queries and consequently a higher workload in the DB than just doing the processing there. That's evident when looking at typical ORM usage (usually very chatty…
You could easily create a new revision of the function you want to change, and have the first box to use the new revision while the rest keep using the old one. In postgres that would be trivial with revision schemas…
A pilot. I'm on my way
I disagree here, Elixir looks similar to Ruby from a syntax perspective. But as soon as you dig into OTP it is a completely new world. It's true that as a beginner you can simply do web development with Phoenix and that…
No processing done at the DB very often implies more queries and consequently a higher workload in the DB than just doing the processing there. That's evident when looking at typical ORM usage (usually very chatty…
You could easily create a new revision of the function you want to change, and have the first box to use the new revision while the rest keep using the old one. In postgres that would be trivial with revision schemas…
A pilot. I'm on my way
I disagree here, Elixir looks similar to Ruby from a syntax perspective. But as soon as you dig into OTP it is a completely new world. It's true that as a beginner you can simply do web development with Phoenix and that…