How do you react to table events using Mnesia's subscription mechanism?

After subscribing, the subscribing process simply receives ordinary messages in its mailbox whenever a matching event occurs, and handles them with a normal receive clause — there's no separate callback registration mechanism the way gen_event handlers work; it's just messages.

mnesia:subscribe({table, session, simple}),

loop() ->
    receive
        {mnesia_table_event, {write, Session, _}} ->
            notify_cache_invalidation(Session),
            loop();
        {mnesia_table_event, {delete, {session, Key}, _}} ->
            evict_from_cache(Key),
            loop()
    end.

Because these arrive as plain messages, a gen_server can subscribe during its init/1 and handle the events in its normal handle_info/2 callback, integrating cleanly with the usual OTP message loop rather than needing a separate event-handling framework layered on top.

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.

Webull! Receive free stock by signing up using the link: Webull signup.