WRT "… If your database tech does this_amazing_thing_that_nobody_else_does, you'd better be goddamn sure you understand the reason why nobody else does it …" I

WRT "… If your database tech does this_amazing_thing_that_nobody_else_does, you'd better be goddamn sure you understand the reason why nobody else does it …" I think several databases actually do this. For example, Alerting in MarkLogic https://docs.marklogic.com/guide/search-dev/alerts#id_29203 https://docs.marklogic.com/guide/search-dev/alerts#id_29203 Another example is Percolations in Elastic Search https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-percolate-query.html https://www.elastic.co/guide/en/elasticsearch/reference/curr... --- My personal view is that those are useful features, however, often they indicate poor architecture where developers did not create proper APIs that put data into the database, and instead rely on database 'triggers' (or percolations/alerts) to notify the 'world' about changes. Those kinds of notifications, should really be coming from either data consumer or data producer APIs, -- not from the database engines.