560 blogs tracked4,950 posts indexed

#software-architecture

8 posts · 4 companies · newest first

1

Flexible Authentication: Reimagining authentication for millions of users at Airbnb (opens on the source site)

Rebuilding login and signup surfaced product insights, not just technical challenges. Here’s how we designed Flexible Authentication at the intersection of product intuition and technical architecture.By: Jose Santos, Mike BarryFor Airbnb, logins at irregular intervals are normal. A guest books a trip in January and may not open the app again until summer. A host checks back only when a reservation comes in, and may be busy with other activities when it does. For a two-sided marketplace where a failed login means a lost booking, and lost revenue for both the guest and the host, long gaps…

infrastructureengineeringexcerpt only · body stays at the source
From the web
2

Sitar-agent: Building a reliable dynamic configuration sidecar at scale (opens on the source site)

How Airbnb built a Kubernetes sidecar to deliver dynamic configuration reliably at scale.By: Bo Teng, Cosmo Qiu, Siyuan Zhou, Ankur Soni, Xin Huang, Willis HarveyIntroductionIn our previous post, we explored Airbnb’s dynamic configuration system, Sitar, with a focus on service architecture and configuration change safety. Now for the harder question: once a config change is committed, which happens several times each minute, how does it actually reach the thousands of Airbnb’s service instances reliably, quickly, and without redeploying the services?This post describes sitar agent: a…

distributed-systemsinfrastructureexcerpt only · body stays at the source
From the web
3

Migrating from a Monolithic Orchestrator to Apache Airflow (opens on the source site)

Photo by Corinne Kutz on UnsplashBefore we knew betterOur orchestration system started as a simple internal solution to manage event pipelines and trigger downstream jobs. Over time, as more workflows and dependencies were added, it gradually evolved into a tightly coupled monolithic scheduler that became increasingly difficult to understand and maintain.Understanding how a workflow executed often meant looking through multiple files, configurations and database tables.For newer team members, onboarding into the system took time because much of the workflow context was distributed across…

etlapache-airflowexcerpt only · body stays at the source
From the web
4

How Bazaarvoice UGC APIs serve information to its brand & retailers (opens on the source site)

Bazaarvoice has thousands of clients including brands and retailers. Bazaarvoice has billions of records of product catalog and User Generated Content(UGC)from Bazaarvoice clients. When a shopper visits a brand or retailer site/app powered by Bazaarvoice, our APIs are triggered. In 2023,Bazaarvoice UGC APIs recorded peak traffic of over 3+ billion calls per day with zero […]

conversations-apisecurityexcerpt only · body stays at the source
From the web
5

Cloud-Native Marvel: Driving 6 Million Daily Notifications! (opens on the source site)

Bazaarvoice notification system stands as a testament to cutting-edge technology, designed to seamlessly dispatch transactional email messages (post-interaction email or PIE) on behalf of our clients. The heartbeat of our system lies in the constant influx of new content, driven by active content solicitations. Equipped with an array of tools, including email message styling, default […]

software-architectureawsexcerpt only · body stays at the source
From the web
6

Data replication across backend services with Kafka and Protobuf (opens on the source site)

The Jobteaser application contains a lot of different relatively independent modules to help universities provide career guidance to students: a job board, a career event management system, a career advice appointment management system…When we decided to migrate our application’s backend from a monolith to a service-oriented architecture, we strived to keep each module as isolated as possible from the others in the event of an incident. If the career appointment system was down, students should still be able to browse and apply to job ads.That isolation is achieved through what we’ve called…

software-engineeringsoftware-architectureexcerpt only · body stays at the source
From the web
7

Layers vs Silos, a tale of 2 microservice architectures (opens on the source site)

When it comes to the communication between microservices, there are 2 possible extremes:All-sync: whenever a service needs data from another service, it fetches it via a synchronous API call (REST, gRPC, GraphQL). Service calls service calls service… which tends to evolve into layers of APIs, where each layer has dependencies on the next.All-async: no sync calls between services, all communication is event-driven or in the form of data replication. This tends to form silos: independent services that are fed all the data they need by an async mechanism and can function independently of any…

microservicesgoexcerpt only · body stays at the source
From the web
8

Our microservice stack (opens on the source site)

This is an introduction to how we’ve implemented microservices at a mid-size scale-up called Jobteaser, with a mix of Go and Ruby service chassis, gRPC APIs and data replication via Kafka.Foundation: The service chassisBack in early 2019, when Jobteaser decided to get serious about breaking up its decade-old Rails monolith into microservices, we assembled a Foundation team that started working on an in-house service chassis.It was soberly coined service and came in two flavours: the rb-service framework in Ruby and the go-service framework in Go. Four years later, they still form the…

microservicesgoexcerpt only · body stays at the source
From the web
8 shown

Privacy choices

Reading never requires analytics. These choices last 90 days on this browser.

Essential sign-in and security storage always stays on. Read the privacy notice.