pREST – A fully RESTful API from any existing PostgreSQL database writting in Go

Re:pREST – A fully RESTful API from any existing PostgreSQL ... by ruslan_talpa on Friday June 23, 2017 @03:53PM (#14622233)

The choice of words might be unfortunate, but the point is that you don't have to change it any more the PostgreSQL/Nginx in order to use and develop apis with it.

[ Parent | on HN ]

Re:pREST – A fully RESTful API from any existing PostgreSQL ... by bpicolo on Friday June 23, 2017 @04:37PM (#14622562)

Unless you have different requirements than the baseline, which is common

[ Parent | on HN ]

Re:pREST – A fully RESTful API from any existing PostgreSQL ... by derefr on Saturday June 24, 2017 @03:02PM (#14626950)

In my experience, most such people just solve this problem by either:

1. submitting an issue to the project's issue tracker, and waiting;

2. submitting an issue to the project's issue tracker, and becoming a project sponsor to expedite;

3. customizing the software using a scripting language it exposes;

4. using a third-party "plugin" for the project that someone else already developed to solve the problem;

5. developing such a plugin yourself, using the software's C FFI API to write your plugin library in your language of choice, rather than the language the software itself is written in;

6. wrapping the software in a single-purpose gateway that decorates or mutates its wire protocol/API with the new features.

In practice, actually modifying the server software itself is very rare. Needlessly rare, even. Some great, clean codebases (Postgres itself; Nginx) get strategies #3-#6 applied so often that there exists a whole ecosystem of features "around" them that really should be in their cores, because everyone was too afraid to touch them even when they're written in common languages.

[ Parent | on HN ]