Skip to content
HomeVideosBooksBlogs
AllTop postsTopics
Podcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K
    K

    Klaviyo Engineering

    klaviyo.tech · Company blog · on HN since 2018

    Klaviyo's engineering team writes about scaling event processing, Graphite metrics, Flink performance, CI problems and using GPT-4 for coding.

    Visit blogHN submissions
    Distributed SystemsDevOps & CloudSystems & Performance
    What HN says

    HN links it mostly in Klaviyo hiring posts, and a Klaviyo engineer commented on how their RabbitMQ/Celery stack compared with DoorDash's.

    Stats for nerds
    15HN people shared it
    23linked in comments
    86story points
    Oct 2020last shared
    2019people per year2020

    Top posts on HN

    1. 1
      Scaling Klaviyo’s Event processing Pipeline with Stream Processing
      2 people · 25 points · first shared 2019 · Discussion on HN
    2. 2
      Scaling Graphite to Millions of Metrics
      2 people · 9 points · first shared 2019 · Discussion on HN
    3. 3
      Calculating π on Pi Day
      1 person · 9 points · first shared 2023 · Discussion on HN
    4. 4
      Poison wheels: a Klaviyo continuous integration fire-fighting story
      1 person · 7 points · first shared 2023 · Discussion on HN
    5. 5
      Optimizing Large State Apache Flink Application for 10x Performance
      1 person · 6 points · first shared 2019 · 1 comments on HN
    6. 6
      Understanding Timings in Distributed Systems
      2 people · 4 points · first shared 2024 · Discussion on HN
    7. 7
      GPT-4 for Coding: 16 Observations and Tips
      1 person · 4 points · first shared 2023 · Discussion on HN
    8. 8
      Fast Visual Testing for Embedded Content
      1 person · 4 points · first shared 2018 · Discussion on HN
    9. 9
      Magic: Constant-time tricks that Klaviyo uses to operate at scale
      2 people · 3 points · first shared 2020 · Discussion on HN
    10. 10
      GPT-4: From strong pair coder to annoying pair coder
      1 person · 2 points · first shared 2023 · Discussion on HN

    What HN people wrote when they linked it

    • zbentleyOct 2020

      This is fascinating. Doordash seems to have encountered many of the same problems we (Klaviyo) did using a RabbitMQ/Celery stack, but arrived at totally different answers. Klaviyo doubled down on making the tools work for us, rather than jumping to a new and untested (for us) broker/job framework technology and arrived at some pretty nice solutions:

      Problems with observability? We added lots of custom StatsD and text logging instrumentation (Celery "signal" middleware), so that we could get e.g. accurate "how long do tasks like this spend waiting in the queue?" answers. Other than the inherent limitation of RabbitMQ being a strict queue (unlike Kafka, you can't "peek" at things in the middle of a topic without consuming that topic--we could do something hyper-complicated with exchanges and deliberate duplication of messages to address this limitation, but that doesn't sound worth it to me at all), observability of the brokers themselves seems pretty good. Coupled with Sentry reporting issues that occur during task processing, and some custom decorators to retry/delay/store tasks affected by common classes of systems issues, our visibility tends to be better than I've seen in any other asynchronous queue/message-bus system I've worked on.

      Sneaky task disappearances turned out to be mostly bugs in the way we were starting/stopping workers, related to signal handling and rabbitmq "redelivery". By really understanding the Celery worker start/stop lifecycle and coupling that…

    • syrneusMay 2019

      Klaviyo | Boston ONSITE | https://www.klaviyo.com | https://klaviyo.tech | http://bit.ly/klaviyocareers

      Klaviyo is a data science company that helps brands grow faster. We're profitable, engineering-driven and growing incredibly fast. We have over 12,000 paying customers and are doubling year over year and ingesting an order of magnitude more data every year.

      We're hiring across the board (Python/Java engineers, systems engineers, site reliability engineers, hands-on team leads, security engineers, data scientists, product managers, designers, and more). We run a DevOps culture and love full stack engineers who code code in both Python and Javascript (we use React and TypeScript).

      Our tech stack is predominantly Python (Django), Java and JS/React running on AWS at massive scale. We run thousands of EC2 boxes, 100s of Aurora MySQL and PostgreSQL clusters and petabyte scale Cassandra clusters. We're heavy users of Kafka, RabbitMQ and Redis. We've just recently launched our first workloads on Kubernetes. We send billions of emails every month and fire customers that send spam--our goal is helping customers have more effective long-term relationships with their customers. We also do push notifications, website personalization and soon SMS.

      We recently raised one of the largest fund-raising rounds in Boston history ($150m) but don't intend to change our core values which includes growing our business organically.

      Feel free to reach out to me at…

    Related

    Uber Engineering Blogeng.uber.com525 people

    Why Uber Engineering Switched from Postgres to MySQL

    Uber Engineering Blog
    Company · last shared 2025
    Russ Coxresearch.swtch.com554 people

    Timeline of the xz open source attack

    Russ Cox
    Personal · last shared 2026
    Twitch Engineering Blogblog.twitch.tv178 people

    Go’s march to low-latency GC

    Twitch Engineering Blog
    Company · last shared 2026
    Wingologwingolog.org237 people

    FFS SSL

    Wingolog
    Personal · last shared 2026
    Zalando Engineering Blogengineering.zalando.com20 people

    Agentic Engineering at Zalando: A Snapshot

    Zalando Engineering Blog
    Company · last shared 2026
    Feldera Blogfeldera.com21 people

    The Pain That Is GitHub Actions

    Feldera Blog
    Company · last shared 2026
    Zendesk Engineeringmedium.com/zendesk-engineering18 people

    Hunting down a C memory leak in a Go program

    Zendesk Engineering
    Company · last shared 2025
    PyPy Blogpypy.org183 people

    PyPy has moved to Git, GitHub

    PyPy Blog
    Company · last shared 2026