Ripped out more orm than written and have been using them since the heyday of toplink…. Yes rapid prototyping, but you pay in pounds of flesh as complexity creepes in as idea matures. Mitigation by maintenance of separation of concerns allows replacement with sql. If you are writing JQL (or equivalent), then you are probably on the edge of a maintenance headache for your replacement.
Scott, you're spot on. While ORMs make for a quick start, they often complicate the project as it grows. The solution is to plan for a flexible architecture in advance that allows for strategy shifts without effort. Designing with modularity from the start is important, preparing for the possibility of integrating direct SQL when needed, ensuring the project remains scalable and maintainable.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ripped out more orm than written and have been using them since the heyday of toplink…. Yes rapid prototyping, but you pay in pounds of flesh as complexity creepes in as idea matures. Mitigation by maintenance of separation of concerns allows replacement with sql. If you are writing JQL (or equivalent), then you are probably on the edge of a maintenance headache for your replacement.
Scott, you're spot on. While ORMs make for a quick start, they often complicate the project as it grows. The solution is to plan for a flexible architecture in advance that allows for strategy shifts without effort. Designing with modularity from the start is important, preparing for the possibility of integrating direct SQL when needed, ensuring the project remains scalable and maintainable.