Andrew, Even if you keep the application servers in another geography, wouldn't it be a performance hit in terms of accessing the Database hosted in another geography? My take would be to keep the systems in the same geography to avoid the performance issues down the line and making the customer dissatisfied.
Secondly, when companies are asking for on-prem versions, you are not left with much of the options as they would be reluctant to open their DB server firewalls to the public cloud where your applications servers would be hosted. This is a compliance thing and every country would have their own rules and regulations anyways wrt to the data security and retention. You are in the best position to assess what your app does and what kind of data it stores and processes, so make a good judgement and don't just think about a middle way to avoid re-architecting some parts of you SaaS design. Sorry if I couldn't understand the complete problem though... Regards, Gagan On 10 August 2018 at 07:15, Andrew Fam <andrew.fa...@gmail.com> wrote: > Hi all, I have a saas solution currently sitting in 1 instance using a > postgres db. > Due to recent expansions, I need to keep the data in the country of which > it came from. e.g Malaysia or Philippines will have a database of their > own. > In addition, some companies are asking for on - prem versions and I was > thinking it might be good for them to own their database while we keep the > application server. > Does anyone have an idea of how to solve this issue and what is the most > elegant way of doing this? > > Some background to this. > I have a tenant model that is storing the country using countryfield. > Some models directly link to the tenant model, others reference a field > which is tied to a model with the tenant model. > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/be6fb573-50fa-4f48-be37-712d1a279859%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/be6fb573-50fa-4f48-be37-712d1a279859%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAM-Jvq5Shvrcksi%3Dhsiyt3S%3D%2Byp1MoP%2Bs77_n6ZyS-yepXTHiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
