Tag Info

New answers tagged

4

Even fetching all details for just one hotel may results in a JOIN query from at least four tables, and scanning over all hotels records. A four-join query is absolutely trivial if you have the appropriate indexes for all joins. The second part of this question is far more troubling. Why the scan over all records? Is is because of missing indexes? ...


2

Why either/or? I've worked very successfully with a hybrid approach, using a relational db (SQL Server, but pick your favourite) to hold data that needs a relational structure - most of this is IDs linking all the various domain objects, very little textual data and certainly no blobs - and a nosql db (Dynamo) to hold large relatively unstructured data, ...


2

NoSQL is generally not very good with relational data. NoSQL is often great for non-relational but structured data like documents or time series. Your "one to many" relationships may look quite like a document: e.g a "hotel" document may carry all its images, room info, etc stored together and fetched with one operation. On the other hand, if you see a ...


4

I think that your search results can greatly improve through a number of techniques or database design approaches that will improve performance in your typical RDBMS. I suggest looking into and possibly prototyping the following improvements to see if they help you in performance testing first before you commit to an entirely new database technology that ...



Top 50 recent answers are included