Thought process between storing data in our own database vs Q2's database

Question

I m not 100 sure I understand this correctly but will do my best trying to explain it I have a bunch of specific user data and other tables I need to create that Q2 database does not have Are my two options Do custom sql to add the necessary columns tables queries Store everything on our end in our own db If we were to store it in q2 s database would the db schema change for everyone Would all q2 developers have access to the data we are storing We are leaning towards storing everything on our end so we have complete freedom on that front to do what we want Only minor issue is each time a new user is created in the q2 database we would have to create a user profile in our db We figured when a new user opens our extension we could create the user profile on the fly Our extension would be communicating with AWS API gateway to access our db Would I need to do any configuring to allow our extension to communicate Do I need to add aws as a vendor in the db Are there steps written somewhere for this My question is is my understanding correct And if you faced the same issue how did you go about deciding the best course of action

Trey Teter · Accepted Answer

Hello A few things to tackle first in general yes store things in your own db If you put things in the q2 db that would change the db schema for whatever environments you are in and q2 would have access to that data Which would be most q2 developers and support personnel Of course we can t just look at production data unless we are authorized to Of course when you run your own database you have that additional freedom The most common practice is when the user navigates to your extension I would use a combination of aba or something from the wedge address config with the user id to create a unique user profile in your own db There is some configuring to do I would recommend running an api in aws so that the extension doesn t directly communicate with the db On that api you can then configure it to be a different url For extensions to access things outside our datacenter they must be whitelisted see https q2developer com support create ticketType Whitelist We will not blanket whitelist the aws domain So that is why I am recommending configuring a different domain Hope this answers your question Trey

Answers