Talk:Embedded database

Document oriented DBMS
What about document oriented databases, such as CouchDB, MongoDB, Riak or Redis? Aren't they in this category? https://en.wikipedia.org/wiki/Document-oriented_database — Preceding unsigned comment added by 46.193.0.40 (talk) 18:48, 12 July 2015 (UTC)

Deletion request
So what is the purpose of this article? 72.54.98.226 (talk) 20:54, 11 August 2010 (UTC)

Software developers working on both open-source and commercial projects, plus computer science professors and computer science students and others need to compare implementations of embedded database management systems to choose the best one for a particular application or to see in depth how theory turns to practice. This page is the natural starting point, and it comes up near the top in Google. The other Google hits are hard to collect into a complete set.Tuolumne0 (talk) 19:40, 15 August 2010 (UTC)

I'm going to remove the deletion request: this is an important page, but I do hope it expands. There is a lot to say about embedded databases. Maybe I'll do that later.Tuolumne0 (talk) 19:57, 15 August 2010 (UTC)

Embedded means how you include the database in your code - and you make the code and the data storage, and start the program by populating your "Embedded database" from files and / or databases. Then you program can store this in shared memory that other processes can access, and they have to use your methods to access the data. Finally, the program has to store all data, so that it is back the next time you start. The articles is far away from discussing this. There are commercial shared memory databases and open source projects, but the reason for preaching "how-to" is because most large projects involves making a central data structure that is accessed by many processes, and the schema is contained in the header files used to compile every process that access it, multi-user access is controlled by semaphores in the shared memory that every process has to include: It is fully possible to read a locked record, but if it happens you may create a mess.KHF 21:45, 9 February 2014 (UTC) — Preceding unsigned comment added by Khflottorp (talk • contribs)

List could be improved
I think the biggest problem with this article is the list of implementations themselves. Some of the ones listed aren't "advertised" as embedded databases and I use the word "advertised" exactly as it should be. The list of implementations is simply a yellow pages list of databases. I think the article should be improved upon and have the list removed. 69.140.155.15 (talk) 17:40, 3 September 2010 (UTC)

Mergers/rearrangement
It sounds like back-end database is the same as an embedded database in the sense of a small standalone DB unified with the application code. Databases for mobile/embedded devices, the second meaning noted in this article, sounds like mobile databases. I think this article is currently listing both types; it makes sense to me to move the second meaning to mobile database and leave this article as the canonical list for the first meaning (or perhaps there is a better title). -- Beland (talk) 02:34, 11 March 2013 (UTC)


 * Disagree. Mobile databases seem to be specific to mobile computers such as phones, while this is not the case with embedded databases. If anything, the merge should be the other way around. --129.21.109.32 (talk) 18:30, 25 September 2013 (UTC)


 * Misleading Embedded databases is a temporary collection of data, usually in shared memory, structured in a way that allows multiple processes to share the same data. "Embedded" here refers to "embedded devices", and what is described is databases in a embedded device. Like iSql is dominant in mobile phones, and that does not make every iSql into an "Embedded Database". Most embedded devices use another database for "persistence" - that allows the memory to be restored the next time the system starts up. Mobile and distributed databases needs the aspect of "replications" - now "synchronisation" and must not be merged with this. I suggest that the article is renamed to "Databases in embedded devices". "Embedded" refers to being embedded in the same address space, an address space that usually will disappear should the program stop, hence the need for a separate storage for persistence. Just now, the article needs major rewriting. E.g. "embedded databases" are often used in middleware (Tibco/OS), used in process automation / SCADA type of systems, where values are gathered in a shared memory, that supplies values, triggers alarms and issue work-orders, and use Oracle and Sybase to provide persistence, to store trend values. KHF 21:32, 9 February 2014 (UTC) — Preceding Khflottorp (talk • contribs)

Proposal to remove non-notable database systems
I've been looking through the logs for this page and a lot of the named databases seem to have no real claim to notability (Dedicated probuct article, an article on their creators, or a cite to an external reference) and have been inserted by editors who only or mainly edit to promote the database system.

I'm planning on removing all databases from this page unless they can exhibit a claim to notability through a link to a wikipedia article or cite a reliable source. Comments? Kiore (talk) 08:08, 25 March 2015 (UTC)

Now done. I haven't got an axe to grind with any of them, if you've got a reasonable claim to notability such as reliable sources for their notability or an existing page please feel free to add any of them back. Kiore (talk) 05:37, 26 March 2015 (UTC)