Buses scheduling - relational database or nosql
I'm trying to store buses schedules into database and I'm wondering which
database model is suitable for my case.
I have bus operators, each operator has several routes, each route has
several turns, each turn has stops, etc. Turns are generated from
something called "turn master" where the scheduling is defined (frequency,
stops, etc.) within next N days.
I expect to deliver a very fast searching for bus when user tries to
search a bus from city to city on given date.
I'm using MySQL, the number of stops reach around 100.000 records and the
searching speed is fast but I'm not sure if it's still fast when data gets
really big (thousand operators, each operator has hundreses turns, each
turn has around 10 stops, turns are generated for around next 30 days).
Basically, performing a search is to look for stop (city/town/place, time)
and check if it matches user search criteria.
So, my question is: Is relational database is best in this case? Or using
some kind of NoSQL will be better when the data get really bigs?
Thanks in advance,
No comments:
Post a Comment