My team is considering utilizing Hibernate/Envers for a granular point in time rollback solution for Redshift data. I have heard that using an ORM with Redshift is not a good idea. Are there particular drawbacks related to using an ORM such as hibernate with Redshift?


There are known drawbacks related to using ORMs, period. They are a result of the inherent impedance between the object-oriented and relational models of the world. These issues will probably be exacerbated by the lack of Redshift-specific Hibernate dialect, and using a Postgres dialect will likely cause additional problems, as many Postgres features are not supported by Redshift.

In short, my opinionated advice would be, don't use an ORM for any non-trivial application, Redshift or not. "[G]ranular point in time rollback solution for Redshift data" doesn't sound like one.

| improve this answer | |
  • ah so there is no redshift-specific Hibernate dialect – mikelus Apr 1 at 23:29
  • Not that I know of, but you should do your own research. And even if it exists, it will not be a magic wand. – mustaccio Apr 1 at 23:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.