Top all-time · #1726
Grab Tech
Company blog · engineering.grab.comprogrammingsystemsdata
Grab Tech is the company blog at engineering.grab.com, writing about programming, systems and data. Since 2016, 43 different Hacker News readers have linked it 61 times, most often “Dealing with the Meltdown patch at Grab”. It is still writing: the last post was on 2026-10-21, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link Grab's engineering blog for posts on logging stacks, mapping, and navigation in Southeast Asia. One commenter calls it pretty high quality, and another says it always has interesting posts.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Grab's Engineering team solves critical transportation challenges and makes transport freedom a reality for 620 million people in Southeast Asia.
Most-linked posts?
- Dealing with the Meltdown patch at Grab2 people · 2 mentions · first linked 2018-01-07
- We Built a Logging Stack at Grab2 people · 2 mentions · first linked 2019-08-04
- Designing Resilient Systems: Circuit Breakers or Retries?2 people · 2 mentions · first linked 2018-12-23
- Enabling near real-time data analytics on the data lake2 people · 2 mentions · first linked 2024-02-23
- Counter Service: How we rewrote it in Rust2 people · 2 mentions · first linked 2025-06-26
- Preventing Pipeline Calls from Crashing Redis Clusters2 people · 2 mentions · first linked 2019-05-14
- Lean and Scalable Data Pipeline to Capture Large Scale Events2 people · 2 mentions · first linked 2019-01-18
- Key Expiration Issues in Redis 2.x2 people · 2 mentions · first linked 2017-03-27
- Troubleshooting Unusual AWS ELB 5XX Error2 people · 2 mentions · first linked 2017-05-11
What Hacker News says?
Elasticsearch apart from being an overkill for logging, I feel has a high cost of maintenance as the system starts to scale. Somehow that cost is not very visible in the start. One of the Singapore based successful start-up (Grab) had blogged about some other pain-points a couple of years back ( https://engineering.grab.com/how-built-logging-stack ) as well.
Comment linking /how-built-logging-stack
on “I don't think Elasticsearch is a good logging system”Submitted Designing Resilient Systems: Circuit Breakers or Retries? as a story · 103 points
HN discussionNot entirely the same thing but navigation and path finding for delivery apps is not a solved problem everywhere. Especially in places where street data isn't complete or works differently (no street names) than in the western cities where Google Maps etc. are developed. Grab ( https://engineering.grab.com ) always has interesting blog posts about these topics like: https://engineering.grab.com/road-localisation-gra…
Comment linking /road-localisation-grabmaps
on “The failure of the Domino's 30-minute delivery guarantee”Submitted Key Expiration Issues in Redis 2.x as a story · 8 points
HN discussionThe Grab engineering blog is pretty high quality, here's a related article from a few years ago that I liked: https://engineering.grab.com/correcting-restaurant-locations...
Comment linking /correcting-restaurant-locations-harnessing-wisdom-of-the-crowd
on “Grab built its own map in Southeast Asia, and is now going after Google”Submitted We Built a Custom Vision LLM to Improve Document Processing at Grab as a story · 4 points
HN discussionThrough my work I got to know this crowdsourcing solution to improve OpenStreetMap street views: https://en.m.wikipedia.org/wiki/KartaView Operated now by Grab: https://engineering.grab.com/kartacam-powers-grabmaps Disclaimer: I work for Grab (but not in the mapping team)
Comment linking /kartacam-powers-grabmaps
on “Ask HN: How to Build Your Own (Mini) Google Street View?”Submitted Designing resilient systems: Circuit Breakers or Retries? as a story · 4 points
HN discussionSubmitted Grab Engineering's Front End Study Guide as a story · 4 points
HN discussionSubmitted Counter Service: How we rewrote it in Rust as a story · 3 points
HN discussionSubmitted Grab AI Gateway: Connecting Grabbers to Multiple GenAI Providers as a story · 3 points
HN discussionSubmitted How Grab built its in-house chat platform for the web as a story · 3 points
HN discussionSubmitted Plumbing at Scale - Event Sourcing and Stream Processing Pipelines at Grab as a story · 3 points
HN discussionSubmitted Preventing Pipeline Calls from Crashing Redis Clusters as a story · 3 points
HN discussionSubmitted Structured Logging: The Best Friend You’ll Want When Things Go Wrong as a story · 3 points
HN discussionSubmitted Orchestrating Chaos Using Grab's Experimentation Platform as a story · 3 points
HN discussionSubmitted Introducing Grab-Kit: Distributed Service Design at Grab as a story · 3 points
HN discussionSubmitted Dealing with the Meltdown patch at Grab as a story · 3 points
HN discussionSubmitted Grab's Mac Cloud Exit Supercharges macOS CI/CD as a story · 2 points
HN discussionSubmitted Counter Service: How we rewrote it in Rust as a story · 2 points
HN discussionSubmitted Ensuring data reliability and observability in risk systems as a story · 2 points
HN discussionSubmitted No version left behind: Our epic journey of Gitlab upgrades as a story · 2 points
HN discussionSubmitted Android App Size at Scale with Project Bonsai as a story · 2 points
HN discussionSubmitted Rethinking Stream Processing: Data Exploration as a story · 2 points
HN discussionSubmitted We Cut GrabFood.com’s Page JavaScript Asset Sizes by 3x as a story · 2 points
HN discussionSubmitted We store and process millions of orders daily as a story · 2 points
HN discussionSubmitted Uncovering the truth behind Lua and Redis data consistency as a story · 2 points
HN discussionSubmitted We Prevented App Performance Degradation from Sudden Ride Demand Spikes as a story · 2 points
HN discussionSubmitted About Being a Principal Engineer at Grab as a story · 2 points
HN discussionSubmitted Catwalk: Serving Machine Learning Models at Scale as a story · 2 points
HN discussion
