Romans Malinovskis has a post on his Medium.com site sharing what he calls a "pragmatic approach to reinventing ORM" with his thoughts about a different approach to this commonly used database interface.
It’s been over a year, since I posted my first highly debated post on Reddit: Reinventing the faulty ORM concept. Gathered information helped me design and implement an alternative pattern to ORM with many important advantages and that has reinforced my belief that ORM is faulty.
He's broken the article up into a few sections with details and thoughts for each along the way:
- Why ORM is important?
- Why ORM is broken?
- How Agile Data differ in approach?
- How Agile Data qualify production/enterprise use?
- Notes on architectural decisions in Agile Data (OOP vs Decoupling)
That final section focuses mostly on the decoupling aspect and the Agile Data library (a Data Mapper) that can be used and solves some of the common ORM problems he mentioned in the earlier sections.