as @JanVladimirMostert mentioned all of those are fine.
if you got a lot of writes -> mongoDB or mysql + toku engine
if you want to use http as default protocol + a functional filter concept + heavy concurrency writes -> couchDB
if you mainly wanna read and validate the data -> liteSQL it was built for that.
databases can scale huge amounts of data these days, you have to think about what you need not about the amount of data unless we're talking about big data which is something like 1,5TB a day or something :)
this would lead to solution like treasuredata or redshift. which are actually file-based databases... but that's a different topic :)
Assuming lakh means 100000, any of those DBs should be fine.
I totally agree esp if it's about searching / filtering :). maybe using mysql as write and elastic as read source. so i have a consistent storage and a good search engine in front of it :)
j
stuff ;)
as @JanVladimirMostert mentioned all of those are fine.
databases can scale huge amounts of data these days, you have to think about what you need not about the amount of data unless we're talking about big data which is something like 1,5TB a day or something :)
this would lead to solution like treasuredata or redshift. which are actually file-based databases... but that's a different topic :)