368 karma · joined July 23, 2015
* Use FDW connections to pull in data from all kinds of sources! Multiple databases, file formats, HTTP buckets, you name it!
* Custom behaviours in multiple languages! PL/Python, PL/Perl, PL/R!
* Read and write to web services! (PL/Python, pgsql-http)
* And now string together arbitrary containers! (pgpodman)
The way the extension system and the type system play together, it really is a very generic place to build weird integrated systems.
https://blog.crunchydata.com/postgis-raster-and-crunchy-brid...
Desktop: https://qgis.org
Middleware: https://mapserver.org, https://geoserver.org, https://mapnik.org, https://github.com/crunchydata/pg_tileserv, https://github.com/crunchydata/pg_featureserv
Web UI: https://openlayers.org, https://leaflet.org, https://www.mapbox.com/mapbox-gljs
Consumers don't see the value at all.
Doctors see the value, but won't pay for it, because it doesn't change their bottom line.
Whose bottom line does this change then?
HMOs, insurance companies, organizations that want to improve the health of a population in aggregate. They'd pay money to have healthier people (on average) to provide the service to their docs (who see the value) to use for free.
Well, maybe; but I was hoping to see that theory validated in the last turn of the wheel.