|
You are here |
yokota.blog | ||
| | | | |
timilearning.com
|
|
| | | | | Have you ever wondered how data stored in databases actually gets represented on your computer's hard disk? Or why some queries to your database tables benefit from adding indexes on columns? Well, whether you have or not, here's a series of posts that aim to detail my understanding of the journey from inserting a row to a database table, to actually retrieving that row. | |
| | | | |
highscalability.com
|
|
| | | | | This is a guest post by Benjamin Manes , who did engineery things for Google and is now doing e... | |
| | | | |
blog.adnansiddiqi.me
|
|
| | | | | In this post, I am going to discuss RocksDB. RocksDB is an embeddable persistent key-value store system developed by Facebook. It was originally forked from LevelDB which was created by Google. According to Wikipedia: RocksDB is a high performance embedded database for key-value data. It is a fork of Google's LevelDB optimized to exploit many | |
| | | | |
my-it-notes.com
|
|
| | | Databases - how they work under the hood?Key takeaways from brilliant book "Designing data intensive application" - to quickly recap core concepts. DB engines classifications Type of load: OLTP (transaction processing) vs OLAP (data warehousing and analytics) Relational vs NoSQL, document vs columnar, graph vs triple-store (semantic facts storage) Even within NoSQL camp you can ... | ||