5 ms·
Interesting article. Having the built in Redis via ETS is slick. I currently use Python but don't use Django but instead wrote my own WSGI frameworks based on
by Timothycquinn 4y ago
Interesting article. Having the built in Redis via ETS is slick.
I currently use Python but don't use Django but instead wrote my own WSGI frameworks based on Flask Restx. I'm not a big believer of ORMs besides their CRUD functionality so there is not much benefit for me using Django and the security burden it carries (like PHP) by being so popular. I can keep my designs light weight, very secure and fast; albeit not nearly as fast as Phoenix.
Note however, I don't build public facing high performance applications so its not critical to have max IO like that which Phoenix can handle.
In a way, I wished I had moved to Elixir but with the technical debt invested in Python its a very big jump. Maybe someday down the road...
- spapas82 4y ago> Interesting article. Having the built in Redis via ETS is slick. This isn't really true. Although having a built in redis may be possible, the fact is that production elixir projects do use redis on a lot of cases (for example as a task queue). ETS is rarely used because of its complexity.
- sph 4y agoRedis might have a nicer API but the ops of maintaining another service is not simpler than just using ETS that is built in the platform. I'd rather choose Redis only iff I hit the limits of ETS. And 99% of apps won't even get to that point.