1,332 karma · joined September 18, 2007
I am good at this stuff. Hire me. My LinkedIn profile is https://www.linkedin.com/in/athikunte/
Location: Bangalore, India
Remote: Yes
Willing to relocate: Yes
Technologies: Java, Elixir, Ruby, Phoenix, LiveView, Postgres, JavaScript, React
Résumé/CV: https://www.linkedin.com/in/athikunte/
Email:
Once your database becomes sufficiently complex you start writing a lot more sql.
ActiveRecord's way of chaining scopes to combine multiple scopes is brittle. You can't customize the conditions. Ecto solves this by giving you composability. You can build on top of your earlier commands. If you combine this with pattern matching in the functions or Enum.reduce you have an extremely powerful and a flexible query engine.
Ecto also relies on the strengths of underlying database engine rather than treating it as a black box. If you are dealing with 100s of tables Rails way of polymorphic design doesn't give you referential integrity. I like Ecto's recommendations: https://hexdocs.pm/ecto/polymorphic-associations-with-many-t...
As businesses realize cash is not easy to scale, and if they are ambitious enough, they will push their customers towards credit/debit cards and other scalable channels.