News for hackers. Stuff that matters.
Re:PostgREST – REST API from any PostgreSQL database by rodgerd on Wednesday July 22, 2015 @05:24AM (#9928510)
In my experience (and I'm older these days...) databases are a much rarer migration than programming languages. I deal with stuff that's still in (heaven help us) VSAM files, accessed a mix of assembler, COBOL, C, Java, TCL, C#, C++, Pascal, and so on and so forth.
Re:PostgREST – REST API from any PostgreSQL database by bdcravens on Wednesday July 22, 2015 @05:34AM (#9928541)
I work on a system has has iterated through 3 distinct languages while relying on the same database.
Re:PostgREST – REST API from any PostgreSQL database by spacemanmatt on Thursday July 23, 2015 @02:46AM (#9934340)
Integrating at the database is a powerful pattern. I see some value for larger organizations to go a step further and integrate at a higher service layer, because one database could never support the entire enterprise. But for orgs that fit in one database, it's great, IMO.
Re:PostgREST – REST API from any PostgreSQL database by spopejoy on Wednesday July 22, 2015 @11:57PM (#9933912)
Agree, the received wisdom has always been database vendor choice as a ten-year commitment, as opposed to almost anything else. It's a reason to avoid databases :)
Re:PostgREST – REST API from any PostgreSQL database by spacemanmatt on Thursday July 23, 2015 @02:44AM (#9934336)
Strongly disagreed that it's a good reason to avoid databases. If you are going to collect data of any value over a long period of time, pick a horse and stay on it. Over time, technology and business needs might force a re-evaluation of that position, but you don't want to build around unmeasured plans to maybe switch databases at random some day.
Re:PostgREST – REST API from any PostgreSQL database by spopejoy on Thursday July 23, 2015 @09:36PM (#9939622)
It was a joke, implying that people who can't commit will avoid databases like the plague