http://charlesleifer.com/blog/using-sqlite-full-text-search-... http://charlesleifer.com/blog/building-the-sqlite-fts5-searc...
2,485 karma · joined November 3, 2009
http://charlesleifer.com/blog/using-sqlite-full-text-search-... http://charlesleifer.com/blog/building-the-sqlite-fts5-searc...
http://charlesleifer.com/blog/building-the-python-sqlite-dri...
Great advice, Albert! I'm glad you like your new job, too :)
http://charlesleifer.com/blog/introduction-to-the-fast-new-u...
http://charlesleifer.com/blog/building-the-sqlite-fts5-searc...
[1] http://docs.peewee-orm.com/
[2] http://docs.peewee-orm.com/en/latest/peewee/playhouse.html#a...
[3] https://github.com/coleifer/peewee/blob/master/examples/redi...
http://charlesleifer.com/blog/sqlite-small-fast-reliable-cho...
I was in part responding to the comment in the "Limitations" section of the README about how Disque was developed in "astronaut mode". Mostly, though, my point was that I think many people use Redis as a queue because they want to use Redis as a queue. Maybe it's already part of the stack, or they like the simplicity, whatever.
I am a huge fan of your work and hope to see Disque succeed, again apologies if you felt I was attacking your project.
http://www.reddit.com/r/unixporn/comments/2mka7r/update_mate...
It's based on Evolve OS.
[1] https://coderwall.com/p/lixing/closure-tables-for-browsing-t...
I wrote some python bindings using ctypes if you happen to be using python:
http://charlesleifer.com/blog/python-bindings-for-unqlite-an...
> An SQLite database is limited in size to 140 terabytes (247 bytes, 128 tibibytes). And even if it could handle larger databases, SQLite stores the entire database in a single disk file and many filesystems limit the maximum size of files to something less than this. So if you are contemplating databases of this magnitude, you would do well to consider using a client/server database engine that spreads its content across multiple disk files, and perhaps across multiple volumes.
Very large amount of traffic:
> SQLite usually will work great as the database engine for low to medium traffic websites (which is to say, 99.9% of all websites). The amount of web traffic that SQLite can handle depends, of course, on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic.
> An SQLite database is limited in size to 140 terabytes (247 bytes, 128 tibibytes). And even if it could handle larger databases, SQLite stores the entire database in a single disk file and many filesystems limit the maximum size of files to something less than this. So if you are contemplating databases of this magnitude, you would do well to consider using a client/server database engine that spreads its content across multiple disk files, and perhaps across multiple volumes.