Re^3: OT: Scalable web application architecture

I have some experience with an online reservation system.

You say that you have 1 database for each property, 400 in total with the same schema. It sounds like you should have all the properties in a single database. You can then link all your pricing, seasons and availablity etc to each property using your unique property id.

My guess is that you are getting slowed down with all the database connects required for each query. Plus you will be repeating the same query on each database (400 times ouch).

mr greywolf

Comment on Re^3: OT: Scalable web application architecture

Replies are listed 'Best First'.
Re^4: OT: Scalable web application architecture by badaiaqrandista (Pilgrim) on Dec 07, 2005 at 23:48 UTC
That's how the database structure when I inherited the software. That's also why I created this 'search cache' thingy. I want to put all things in one table to speed up searching. But it becomes too overloaded with SELECT, INSERT, and UPDATE queries at the same time. Changing the whole database structure is something I don't want to do right now because we don't have automated test that can give me security in mind. badaiaqrandista	[reply]

Replies are listed 'Best First'.

Re^4: OT: Scalable web application architecture
by badaiaqrandista (Pilgrim) on Dec 07, 2005 at 23:48 UTC

That's how the database structure when I inherited the software. That's also why I created this 'search cache' thingy. I want to put all things in one table to speed up searching. But it becomes too overloaded with SELECT, INSERT, and UPDATE queries at the same time.

Changing the whole database structure is something I don't want to do right now because we don't have automated test that can give me security in mind.

[reply]