Handling Application Architecture
The long story short is, I currently have a fairly standard full stack app running. It's a mailing list and the frontend shows some Posting info as well (https://apptrack.tech is the website for reference).
I'm trying to add a new application to accompany this. I really wanna use t3 stack for dev speed + nextauth is just super easy. My main issue is that my new app's data needs to have relations to the Postings in my original databse. I'm really lost on how to begin integrating these two and would love some help.
2 Replies
do you mean relations in the database sense
is it on another domain/sub domain
do they need seperate DBs
the intention is for it to be separate db's, though if that makes things so much harder that it's not worth it, i suppose they could use the same db
currently on separate domains (one's on supabase the other railway)
and yea, in the db sense
so original db has a "Posting". if i show a user that posting and they wanna save it, or like it, or any interaction, i wanna have a row in a "Saves" table like
userId: 12 | postId: 9862