design – How does a database update trigger a notification to application layer?


Application component 1(ap1) record/insert/update a new state in graph database(neo4j)

For every new state change in the database, application component 2(ap2) needs to be informed/notified that a new entry(event) is made. ap2 would not like to poll database and track/find for state change.

enter image description here


Both application components will be written in GoLang

Database supports triggers & Stored procedures functionality. It is neo4j database.

OS Environment is Linux

I came acros this article: http://graphdb.ontotext.com/documentation/free/notifications.html

What is the design pattern to make ap2 listen to any new event(immediately) on a database update? without ap2 tracking & polling state changes in database