-
MemQ Pub/Sub + Kafka @ Pinterest
Data Flow MemQ Components Storage MemQ Data format Takeaways: References:
-
Postgresql -> Cockroach DB
Context: Options for Horizontally scalable databases (to be performant as datasize becomes larger) Decided at the time that Cockroach DB was the best solution. Migration steps required Rewriting incompatible SQL code Load testing Migration When to use CockroachDB? Who uses CockroachDB? Special mentions: Ref:
-
SLATE Testing At Uber
The Traditional Approaches are below Testing Requirements: SLATE Tools to support SLATE testing Takeaways: Ref:
-
How Netflix Makes Product Decisions?
Below: Netflix’s A/B test Tooling back in 2001 Takeways: Ref: Original Blog Netflix Culture Netflix AB Testing
-
Reduce Logging Costs at Uber with CLP
Logging Architecture How CLP Works CLP Implementation in Hadoop Environment Invented Custom Floating Point Encoding Finally: Ref: Original Blog Lossless vs lossy compression Zstandard
-
OLTP and OLAP at Grab
OLTP OLAP Final Data ingestion pipeline Personally not sure about the reason for introducing Kafka. Maybe there are other clients besides MySQL Implemented Client side out of order message updates: Takeaways: Ref:
-
Why Trello Chose Kafka over RabbitMQ?
RabbitMQ RabbitMQ implementation looks like a separation of concern however, when there are any issues during the operation, there is a synchronous failure on many parties. Hence RabbitMQ is not exactly an ideal distributed queue system. Bad things happen when a failure occurs: Three ways a failure can occur: Network issues happen very frequently, I…
-
Scaling Bloated PostgreSQL DB
Table Bloats Index Bloats How to Prevent Bloat How to Reduce Bloat No one wants to use pg_repack or pgcompacttable when there is no problem with bloat. Another tool not mentioned in the article is pg_squeeze focused on tackling similar bloat issues. DB Major Upgrades (not related to scaling but is also in article) DB…