Pinterest's profile on StackShare is not actively maintained, so the information here may be out of date.

Decisions 5

James Man

Software Engineer at Pinterest

Shared insights

One of our top priorities at Pinterest is fostering a safe and trustworthy experience for all Pinners. As Pinterest’s user base and ads business grow, the review volume has been increasing exponentially, and more content types require moderation support. To solve greater engineering and operational challenges at scale, we needed a highly-reliable and performant system to detect, report, evaluate, and act on abusive content and users and so we created Pinqueue.

Pinqueue-3.0 serves as a generic platform for content moderation and human labeling. Under the hood, Pinqueue3.0 is a Flask + React app powered by Pinterest’s very own Gestalt UI framework. On the backend, Pinqueue3.0 heavily relies on PinLater, a Pinterest-built reliable asynchronous job execution system, to handle the requests for enqueueing and action-taking. Using PinLater has significantly strengthened Pinqueue3.0’s overall infra with its capability of processing a massive load of events with configurable retry policies.

Hundreds of millions of people around the world use Pinterest to discover and do what they love, and our job is to protect them from abusive and harmful content. We’re committed to providing an inspirational yet safe experience to all Pinners. Solving trust & safety problems is a joint effort requiring expertise across multiple domains. Pinqueue3.0 not only plays a critical role in responsively taking down unsafe content, it also has become an enabler for future ML/automation initiatives by providing high-quality human labels. Going forward, we will continue to improve the review experience, measure review quality and collaborate with our machine learning teams to solve content moderation beyond manual reviews at an even larger scale.

46 2.8M

Ashish Singh

Tech Lead, Big Data Platform at Pinterest

To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

#BigData #AWS #DataScience #DataEngineering

38 3M

Jigar Shah

Security Software Engineer at Pinterest

Security team builds services, solutions and tools for teams within Pinterest to manage accesses of critical production resources as well as facilitate adding authentication, authorization and accounting within critical production micro-services. Issuing identities to > 130k AWS EC2 instances, using them to make authentication and authorization decisions high bandwidth critical traffic flow conditions while services communicate in a mesh, requires a great deal of performance and stability. GoLang provides exactly that. Also primary engineering skills in Security team need not to be fully familiar with complex programming logic requires in Java/Kotlin while avoiding the pitfalls on runtime failures or uncertain behavior using Python in production leads us to GoLang

9 1.4M

Jigar Shah

Security Software Engineer at Pinterest

A consistent plane across teams at Pinterest to achieve deploy orchestration using EC2 APIs underneath.

2 1.3M

Blog Posts 238

Jan 4 2024 at 8:19PM
by Pinterest Engineering
Dec 21 2023 at 2:43PM
by Pinterest Engineering
Nov 28 2023 at 10:18PM
by Pinterest Engineering
Nov 22 2023 at 7:20PM
by Pinterest Engineering

Open Source 72

PubSubClient (PSC)
0 3
Transformer-based Realtime User Action Model for Recommendation at Pinterest
0 1

Tech Talks 17

by Pong Eksombatchai One of the primary engineering challenges at Pinterest is how to help people discover ideas they want to try, which means serving the right idea to the right person at the right time. While most other recommender systems have a small pool of possible candidates (like 100,000 film titles on a movie review site), Pinterest has to recommend from a catalog of more than 4+ billion ideas. To make it happen, we built Pixie, a flexible, graph-based system for making personalized recommendations in real-time. iTunes App Store: Google Play:
by Ekrem Kocaguneli Welcome to Pinterest’s home-sweet-Home Feed. Ekrem starts by giving you the ins and outs of how Pinterest’s highly personalized Home Feed works, then explains how we use machine learning techniques to rank the Pins you find there and fully personalize the experience.​ iTunes App Store: Google Play:
by Justin Mejorada-Pier & Charlie Gu In this talk, Justin and Charlie run through the challenges they faced while building in-house tools like DataHub (the primary way people run queries and mine data here at Pinterest). Tune in as they share the hard-won learnings they picked up along the way. iTunes App Store: Google Play:
by Jenny Liu Learn how we built the web-scale recommender system that powers over 40% of user engagement on Pinterest. Jenny will discuss how the small but mighty team prioritized the simplest and highest-leverage solutions. She’ll also give a rundown of the many challenges and learnings that came up in the evolution of candidate generation, Memboost and ranking in our system.​ iTunes App Store: Google Play: