You might be thinking, I don't need an ORM engine. I don't even know what ORM means! I know SQL backwards and forwards so there's nothing an ORM can offer me. Maybe you've had experience with other ORM engines, whether CFML-based or not, and the experience was less that ideal. Why should you consider Quick?
Quick's ORM philosophy comes down to three main points:
Quick was built out of lessons learned and persistent challenges in developing complex RDBMS applications using built-in Hibernate ORM in CFML.
- Hibernate ORM error messages often obfuscate the actual cause of the errorbecause they are provided directly by the Java classes.
- Complex CFML Hibernate ORM applications can consume significant memory andprocessing resources, making them cost-prohibitive and inefficient when usedin microservices architecture.
- Hibernate ORM is tied to the engine releases. This means that updates comeinfrequently and may be costly for non-OSS engine users.
- Hibernate ORM is built in Java. This limits contributions from CFMLdevelopers who don't know Java or don't feel comfortable contributing to aJava project.
- Hibernate ORM doesn't take advantage of a lot of dynamic- andmeta-programming available in CFML. (Tools like CBORM have helped to bridgethis gap.)
We can do better.