Hacker News Reader

Comment by danbruc | Hacker News Reader

In which case you are connecting to a web server that connects to a database, you are not connecting to a database.

To be pedantic here, you're never connecting directly to a database, but rather to a DBMS, and it's nowhere set in stone that the DBMS must not offer a web interface.

That's not entirely true. You can absolutely load underlying data structures into your own application, and in fact this is how a lot of older database tech used to be. Stuff like dBase, Access, etc., used to be literally "load database into program memory" or "read database format from file" - similar to what SQLite does now.

I wonder if CSS could implement sqlite...

But even in that case you are - at least usually - still interacting with some kind of DBMS. I am not really familiar with the examples you named but with SQL Server Compact you are essentially just loading and running the DBMS in your process. But as I said in my other reply, at some point the distinctions become blurry.

I'd propose the litmus test for this is "can it initiate action on its own, or does it require your code to do so." In this vein, SQLite is not actually a DBMS while Postgres is. The actual Management System parts are things that handle backup, replication, auth, logging, etc.

The database parts are dealing with areas that must have some triggering action (calling a stored procedure, running a trigger, selecting a resultset, that kind of thing) for anything to happen.

The lines are blurring, yes. What's interesting is the 4GL systems which do the reverse (colocate your apps with your data for speed).

I think that definition is way to narrow, the management in DBMS refers to managing the data, keeping it consistent, laying it out on disk and in memory, reading, updating and deleting it. To address the things you named, DBMSs are not required to support backups or replication, authentication and logging happens during actions you initiate.

I mostly use database instead of DBMS because nobody calls it a DBMS, at best a database or SQL server. And I actually wondered for a short moment whether there is any DBMS with a web server. But I would probably still argue that you are connecting to a web server that just happens to be integrated into the DMBS. But admittedly at some point this turns into a matter of point of view and personal preference how to slice the system and label the components.

And I actually wondered for a short moment whether there is any DBMS with a web server.

I don't know if it's still the case or not, but Oracle had the option to run a web-server as part of the database at one time. Back in the Oracle 8 or Oracle 9 era, as best as I can remember.

EDIT:

OK, here we go.

https://docs.oracle.com/en/database/oracle/oracle-database/1...

You can use an embedded version of the PL/SQL gateway that runs in the XML DB HTTP Listener in the database. It provides the core features of mod_plsql in the database but does not require the Oracle HTTP Server. You configure the embedded PL/SQL gateway with the DBMS_EPG package in the PL/SQL Web Toolkit.

Some advantages of using the embedded gateway instead of mod_plsql are:

You can invoke PL/SQL web applications like Application Express without installing Oracle HTTP Server, thereby simplifying installation, configuration, and administration of PL/SQL based web applications.

You never connect to a DBMS. Everything you're doing to interact with it, or a web server is mediated by your OS. You just open sockets and the connection is handled by TCP or IPC or whatever.

(╯°□°)╯︵ ┻━┻

You never really open a socket, you really only push and pull some electrons around and then...

Did you see that post from last week https://blog.polyglot.network/backend.sql-+-frontend.js-love?

You can set arbitrary headers with postgrest so you can use it to serve pages. I don't know if this is exactly what you mean but it's as close to "dbms with its own web server" as I've seen.

It's also just cool lol. Though as much as I like plpgsql and it would be hilarious to use it as a templating engine I don't really have a use for this.

CouchDB famously has an HTTP protocol.

I've seen a few DBs accessible through a REST API.

Several are only accessible through a HTTP REST API, even.

E.g. I'm not aware of an, out of the box, elasticsearch interface that is not the HTTP API.

This is pure five-minutes-of-serching knowledge, but it seems that Elasticsearch is not a database but a search engine build on top of Lucene.

Reply on news.ycombinator.com