WebSocket with free RDMBS (PostgreSQL, SQLite, etc.) And without a JavaScript ecosystem

Question

I am looking for a simple implementation for moving from a free relational database (PostgreSQL, MySQL, SQLite, etc.) to client browsers via WebSocket or WebPush .
I want to avoid the whole ecosystem of JavaScript on the server side (Node.js, npm and cie) and the NoSQL database.
Everything should be hosted on my company's servers, I can’t use third-party services.

I found these interesting solutions:

• http://initd.org/psycopg/articles/2010/12/01/postgresql-notifications-psycopg2-eventlet/ [with Python]
• https://gist.github.com/drocco007/6e44ac1a581546c16e67 [the same has improved slightly]
• https://coussej.imtqy.com/2015/09/15/Listening-to-generic-JSON-notifications-from-PostgreSQL-in-Go/ [with Go]

Do you know other ways to do this?
Is PostgreSQL a more suitable free RDBMS for this?
Can this be done using a SQLite database?
Can the capabilities of Apache or NGinx be used to achieve this?

Answer 1

Update 01/23/17: I wrote an application called postgresql2websocket to send PostgreSQL notifications via websites using Python 3 with asynchronous + aiohttp + asyncpg https://github.com/frafra/postgresql2websocket ; you can combine it with PostgREST to have both standard REST APIs and real-time updates using WebSockets.

As far as I know, there is no HTTP server extension for using SQL databases with web sites without any visits.

You can use server-side Python, for example: real-time web applications using (only) Python and Postgres . I think this can be improved thanks to aiopg . If you don't need Websockets, you can just use ngx_postgres .

If you like Django, Django Channels will probably be included in Django 1.10 (Redis / in-memory / ... layer for channels and SQL server).

You can use SQLite, but keep in mind that you need to implement a server-side publish / subscribe mechanism (like the Django channel), because SQLite does not have this.

If you're just interested in a pub / sub on top of Websockets, you can use Webdis (a solution based on Redis): this will probably be easier than a full SQL database.