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
    P

    PayPal Tech Blog

    medium.com/paypal-tech · Company blog · on HN since 2021

    PayPal's engineering blog on Medium, covering Kubernetes scaling, Kafka, PostgreSQL, JunoDB, Spark on GPUs and API design.

    Visit blogHN submissions
    Distributed SystemsDatabasesDevOps & Cloud
    What HN says

    HN commenters link it for the JunoDB open-source announcement and for Braintree's post on Postgres schema changes and lock behavior.

    Stats for nerds
    16HN people shared it
    29linked in comments
    129story points
    Apr 2024last shared
    2021people per year2024

    Top posts on HN

    1. 1
      Scaling Kubernetes to Over 4k Nodes and 200k Pods
      4 people · 49 points · first shared 2022 · 4 comments on HN
    2. 2
      Spark 3 and GPUs to Reduce Cloud cost by up to 70%
      3 people · 13 points · first shared 2024 · 1 comments on HN
    3. 3
      PostgreSQL at Scale: Saving Space (Basically) for Free
      2 people · 13 points · first shared 2021 · 1 comments on HN
    4. 4
      We Solved the Thundering Herd Problem
      3 people · 9 points · first shared 2022 · Discussion on HN
    5. 5
      GraphQL at PayPal: An Adoption Story
      1 person · 9 points · first shared 2021 · 4 comments on HN
    6. 6
      Using Documentation-Driven Design to Guide API Decisions
      2 people · 4 points · first shared 2021 · Discussion on HN
    7. 7
      Scaling Kafka Consumer for Billions of Events
      1 person · 4 points · first shared 2021 · Discussion on HN
    8. 8
      How PayPal Uses Real-time Graph Database and Graph Analysis to Fight Fraud
      1 person · 3 points · first shared 2021 · Discussion on HN
    9. 9
      Pre-Mortem: Working Backwards in Software Design
      1 person · 3 points · first shared 2021 · Discussion on HN
    10. 10
      How We Built a Shared UI Component Library
      1 person · 3 points · first shared 2022 · Discussion on HN

    What HN people wrote when they linked it

    • winwangApr 2024

      Let's assume a cloud datacenter context, using GCP as an example for real, verifiable numbers.

      An L4 GPU node (with 4 CPU cores) is approximately the cost of a 16-core VM. So for the price of 64 cores, you could have ~4 L4 nodes (or perhaps one VM with 4 L4s). Each GPU has 300 GB/s of memory bandwidth, which is approximately 60 cores worth (at ~5GB/s per core). In fact, the 64 "cores" are typically 32 physical cores only, so you would expect lower than 300 GB/s for a 64-core VM.

      Let's say network I/O is between 10 Gbits/s and 800 Gbits/s. PCIe 4.0x16 is 64 GB/s, i.e. 512 Gbits/s. PCIe 5.0x16 is double that, which would easily saturate the network link. Also, L4 GPUs have RDMA enabled, bypassing the CPU when ingesting data. I also highly doubt that a 64-(v)core VM can access ">100 PCIe lanes" unless you have some kind of sole tenancy setup.

      Then, what if: instead of 4 L4 GPUs (which would have a similar cost to the 64-core node), you used 2 L4 GPUs and found that setup to process just as fast as your 64-core node? You'd have just halved your cost.

      Of course, this depends on whether or not the GPU nodes actually process your data with the same SLA, but generally GPU network ingest > CPU network ingest (per $ of processing).

      Here's some benchmark results from Voltron Data (I'm not affiliated with them): https://voltrondata.com/benchmarks/theseus

      Here's more data from PayPal:…

    • brasetvikNov 2021

      Thanks for the background :)

      Lock behaviour of migrations are indeed very important to be aware of.

      Braintree (which are heavy Postgres users) have a pretty good post on that - https://medium.com/paypal-tech/postgresql-at-scale-database-schema-changes-without-downtime-20d3749ed680

    • yftsuiOct 2023

      @dang The link should be pointing to the actual PayPal article https://medium.com/paypal-tech/unlocking-the-power-of-junodb-paypals-key-value-store-goes-open-source-ee85f935bdc1.

      Here is the archive link https://archive.ph/etRgW

    Related

    Uber Engineering Blogeng.uber.com525 people

    Why Uber Engineering Switched from Postgres to MySQL

    Uber Engineering Blog
    Company · last shared 2025
    Datadog Blogdatadoghq.com262 people

    Husky, Datadog's Third-Generation Event Store

    Datadog Blog
    Company · last shared 2026
    Mesosphere Blogmesosphere.com150 people

    Docker vs. Kubernetes vs. Mesos

    Mesosphere Blog
    Company · last shared 2019
    Google Cloud Platform Blogcloudplatform.googleblog.com349 people

    Introducing Cloud Spanner, a Global Database Service

    Google Cloud Platform Blog
    Company · last shared 2026
    Databricks Blogdatabricks.com298 people

    DBRX: A new open LLM

    Databricks Blog
    Company · last shared 2026
    Codeship Blogblog.codeship.com138 people

    Crystal: Fast as C, Slick as Ruby

    Codeship Blog
    Company · last shared 2020
    Tigris Blogtigrisdata.com37 people

    Nomadic infrastructure design for AI workloads

    Tigris Blog
    Company · last shared 2026
    Robinhood Engineeringrobinhood.engineering19 people

    Faust: Stream Processing for Python

    Robinhood Engineering
    Company · last shared 2022