Arpit’s Newsletter

Arpit's Newsletter focuses on empowering software engineers by enhancing their learning capabilities, soft skills like active listening and extreme ownership, and technical skills including multi-threading, database management, and understanding complex systems. It also explores how companies like Shopify, Slack, Twitter, and Grab tackle scalability, data management, and service reliability.

Career Development Software Engineering Practices Databases Multi-threading API Design System Design Scalability and Performance Company Case Studies

The hottest Substack posts of Arpit’s Newsletter

And their main takeaways
176 implied HN points 26 Apr 23
  1. In databases, you can use DATE, DATETIME, or TIMESTAMP data types to store date and time information, each with its own range of values.
  2. DATETIME is best for storing static timestamps like appointment schedules, while TIMESTAMP is ideal for recording event timestamps with efficient storage and automatic timezone handling.
  3. Consider factors like range, storage requirements, and use cases when choosing between DATETIME and TIMESTAMP for accurate and efficient temporal data storage.
Get a weekly roundup of the best Substack posts, by hacker news affinity:
78 implied HN points 29 Mar 23
  1. SQL databases use B+ trees for efficient data operations like insert, update, find, and delete.
  2. Storing data in sequential files can lead to inefficiencies for database operations.
  3. B+ trees enable efficient CRUD operations and range queries with time complexity O(log n).
58 implied HN points 01 Mar 23
  1. Shopify uses a distributed architecture with pods to handle a large number of shops sharing the same database.
  2. Shopify balances database shards without downtime by moving shops between pods using a tool called ghostferry.
  3. To ensure no downtime or data loss, Shopify follows three phases when moving a shop from one pod to another: batch copy, prepare for cutover, and cutover and updating the routing.
3 HN points 08 Feb 23
  1. Twitter uses Elasticsearch (ES) for search because it provides speed, performance, and scalability.
  2. Twitter built an Elasticsearch Proxy to ensure cluster efficiency, stability, and provide standardized access.
  3. Twitter implemented an Ingestion Service and Backfill Service to manage massive data ingestion into Elasticsearch clusters.