Jump to content

Database-as-IPC

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Chaos5023 (talk | contribs) at 18:31, 1 April 2016 (Undid revision 712910692 by 90.230.33.170 (talk) link is fine, possibly a transitory failure (and in any event you should at least try to convert to an archive link before deleting)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In computer programming, Database-as-IPC is an anti-pattern where a database is used as the message queue for routine interprocess communication in a situation where a lightweight IPC mechanism such as sockets would be more suitable. Using a database for this kind of message passing is extremely inefficient compared to other IPC methods and often introduces serious long-term maintenance issues, but this method enjoys a measure of popularity because the database operations are more widely understood than "proper" IPC mechanisms.[1]

References

  1. ^ 5 subtle ways you’re using MySQL as a queue, and why it’ll bite you Schwartz, Baron. 2011 September 14.


Stub icon

This computer science article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Database-as-IPC&oldid=713062694"