News for hackers. Stuff that matters.

A comment on Show HN: Write universally accessible SQL, not library-specific ORM wrapper APIs. Parent comment

Re:Show HN: Write universally accessible SQL, not library-sp... by _moof on Tuesday August 10, 2021 @12:24PM (#28130787)
In my experience this is an overrated concern. And when it does happen, it's usually accompanied by a rewrite anyway.
[ Parent | on HN ]
Re:Show HN: Write universally accessible SQL, not library-sp... by tomrod on Tuesday August 10, 2021 @12:33PM (#28130901)
Mid and low tail risk applications, certainly.

Some applications have regulatory requirements associated with them, especially retention, or otherwise serve critical needs areas.

[ Parent | on HN ]
Re:Show HN: Write universally accessible SQL, not library-sp... by refactor_master on Tuesday August 10, 2021 @01:05PM (#28131345)
> Some applications have regulatory requirements associated with them, especially retention, or otherwise serve critical needs areas.

Which is why the choice ends up between “keep a legacy system older than the average age in the IT industry” and “take it apart and start over”.

[ Parent | on HN ]
Re:Show HN: Write universally accessible SQL, not library-sp... by _moof on Tuesday August 10, 2021 @12:52PM (#28131137)
My experience includes government, consumer unicorns, and new vehicle development in aerospace. I'm familiar with highly regulated and exponential-growth settings.
[ Parent | on HN ]
Re:Show HN: Write universally accessible SQL, not library-sp... by tomrod on Tuesday August 10, 2021 @03:27PM (#28133082)
Me too! And my experience notes that it is exactly-rated, versus under-rated.
[ Parent | on HN ]