Door Number One#
We test out a "do it all in one swoop" with some established patterns approach.
Given light context to help it out.
Prompt:
I want to add an ability to follow a given tag and receive notifications when someone publishes a new link to it. For example, I should be able to follow "vtuber" and see all posts with the "vtuber" tag. This should be stored in postgres, but handled with ETS in the beginning. Once the user sees the notification, we write it as viewed to postgres and keep the old log of them there. The table will grow eventually, but we will simply implement a chronological truncation strategy since we dont care about keeping notifications long term.
This should be a relationship creating a new idea of following a given user in the postgres database. A user can have thousands of followers. This should be a join table by default to keep things slim.
Handle any domain logic through one master context that controls everything needed for these premises.
This should centralize around @user.ex @tag.ex @bookmark_tag.ex and it should be shown in the application as a tray with a dropdown that shows you each new link that user posted.