Home/ Questions/Q 8902891
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T01:43:47+00:00

The system I’m working is structured as below. Given that I’m planning to use

  • 0

The system I’m working is structured as below. Given that I’m planning to use Joomla as the base.

enter image description here

a(www.a.com),b(www.b.com),c(www.c.com) are search portals which allows user to to search for reservation.

x(www.x.com),y(www.y.com),z(www.z.com) are hotels where booking are made by users.

All a,b,c,x,y,z runs the same system. But they should have separate domains. So according to my finding and research architecture should be as above where an API integrate all database calls.

Given that only 6 instance are shown here(a,b,c,x,y,z). There can be up to 100 with different search combinations.

My problems,

Should I maintain a single database for the whole system ? If so how can I unplug one instance if required(EG : removing http://www.a.com from the system or removing http://www.z.com from the system) ? Since I’m using mysql will it not be cumbersome for the system due to the number of records?

If I maintain separate database for each instance how can I do the search? How can I integrate required records into one and do the search?

Is there a different database approach to be used rather than mentioned above ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem you describe is “multitenancy” – it’s a fairly tricky problem to solve, but luckily, others have written up some useful approaches. (Though the link is to Microsoft, it applies to most SQL environments except in the details).

    The trade-offs in your case are:

    • Does the data from your hotels fit into a single schema? Do their “vacancy” records have the same fields?
    • How many hotels will there be? 3 separate databases is kinda manageable; 30 is probably not; 300 is definitely not.
    • How large will the database grow? How many vacancy records?
    • How likely is it that the data structures will change over time? How likely is it that one hotel will need a change that the others don’t?

    By far the simplest to manage and develop against is the “single database” model, but only if the data is moderately homogenous in schema, and as long as you can query the data with reasonable performance. I’d not worry about putting a lot of records in MySQL – it scales very well.

    In such a design, you’d map “portal” to “hotel” in a lookup table:

    PortalHotelAccess

    PortalID   HotelID
-----------------
A          X
B          X
B          Y
C          X
C          Y
C          Z
    • 0