Database-as-IPC

<p>In <a href="/facts/Computer_programming/QmSsFnu0">computer programming</a>, Database-as-<a href="/facts/Inter-process_communication/cIQYyT6y">IPC</a> may be considered an <a href="/facts/Anti-pattern/BSSJC6os">anti-pattern</a> where a disk persisted table in a database is used as the message queue store for routine <a href="/facts/Inter-process_communication/cIQYyT6y">inter-process communication</a> (IPC) or subscribed data processing. If database performance is of concern, alternatives include <a href="/facts/Unix_domain_socket/fHCylnmJ">sockets</a>, <a href="/facts/Network_socket/r1ldfkb5">network socket</a>, or <a href="/facts/Message_queue/Kq7kX86w">message queue</a>.
</p><p>British <a href="/facts/Computer_scientist/DavggjGL">computer scientist</a>, Junade Ali, defined the Database-as-IPC Anti-Pattern as using a database to "schedule jobs or queue up tasks to be completed", noting that this anti-pattern centres around using a database for temporary messages instead of persistent data.
</p>

Database-as-IPC open-in-new

Database-as-IPC