When is BIG, big enough for a database?

Posted by David ??? on Stack Overflow See other posts from Stack Overflow or by David ???
Published on 2011-01-11T11:52:14Z Indexed on 2011/01/11 13:54 UTC
Read the original article Hit count: 128

Filed under:
|
|
|

I'm developing a Java application that has performance at its core. I have a list of some 40,000 "final" objects, i.e., I have an initialization input data of 40,000 vectors. This data is unchanged throughout the program's run.

I am always preforming lookups against a single ID property to retrieve the proper vectors. Currently I am using a HashMap over a sub-sample of a 1,000 vectors, but I'm not sure it will scale to production.

When is BIG, actually big enough for a use of DB? One more thing, an SQLite DB is a viable option as no concurrency is involved, so I guess the "threshold" for db use, is perhaps lower.

© Stack Overflow or respective owner

Related posts about java

Related posts about database