Explore >> Select a destination
|
You are here 
|
www.confluent.io | ||
| | | | |
henrikwarne.com
|
|
| | | | | What a great book Designing Data-Intensive Applications is! It covers databases and distributed systems in clear language, great detail and without any fluff. I particularly like that the author Martin Kleppmann knows the theory very well, but also seems to have a lot of practical experience of the types of systems he describes. There is... | |
| | | | |
jeff.klukas.net
|
|
| | | | | Originally posted on the Simple engineering blog; also presented at PGConf US 2017 and Ohio LinuxFest 2017 We previously wrote about a pipeline for replicating data from multiple siloed PostgreSQL databases to a data warehouse in Building Analytics at Simple, but we knew that pipeline was only the first step. This post details a rebuilt pipeline that captures a complete history of data-changing operations in near real-time by hooking into PostgreSQL's logical decoding feature. The new pipeline powers not only a higher-fidelity warehouse, but also user-facing features. | |
| | | | |
curatedsql.com
|
|
| | | | | ||
| | | | |
timilearning.com
|
|
| | | Distributed databases typically divide their tables into partitions spread across different servers which get accessed by many clients. In these databases, client transactions often span the different servers, as the transactions may need to read from various partitions. A distributed transaction is a database transaction which spans multiple servers. This post will detail how databases guarantee some ACID properties when executing distributed transactions. | ||
