Read what ships.

01Amazon Web Services · architecture

Automate medical coding with Step Functions and Amazon Bedrock AgentCore

Automating medical coding requires a hybrid approach that combines deterministic orchestration with bounded agentic reasoning to ensure safety, auditability, and human oversight. The team built a workflow using AWS Step Functions, AWS Lambda, and Amazon Bedrock AgentCore that evaluates terms cheapest-first via block-lists, exact matching, and finally an LLM agent for ambiguous cases. This design successfully autocodes confident cases while routing ambiguous ones to human reviewers with full audit trails and decision explanations.

DEPTH ■■■■■15 min read4 days ago

AWS

Sign in to save and rate

02GitHub · architecture

The bridge to agent-scale Git infrastructure

GitHub faced infrastructure capacity limits and a 25ms cross-region network round trip when migrating repositories to Azure. The team changed the storage quorum from repository-wide locks to per-reference serialization and introduced ephemeral virtual replicas backed by object storage. This raised write throughput, prevented slow replicas from blocking traffic, and decoupled read scaling from the write quorum.

DEPTH ■■■■■8 min read4 days ago

Infrastructure

Sign in to save and rate

03Grab · architecture

App stability at scale with a layered defense

To maintain app stability amidst rapid weekly releases and AI-generated code, Grab uses a layered defense strategy covering prevention, release gates, and incident response. This pipeline includes static analysis via custom lint rules, multiple tiers of automated and manual testing, a pre-production early access build, staged rollouts, and feature flags with instant kill switches. As a result, critical defects are caught early in the development lifecycle before reaching the wider production user base.

DEPTH ■■■■■16 min read4 days ago

MobileReliability

Sign in to save and rate

04Fly.io · migration

SBD: We Have a Filesystem at Home

Fly.io replaced a custom JuiceFS-based filesystem for their Sprites infrastructure with the Sprites Block Device (SBD) to eliminate complex, out-of-sync metadata ledgers. SBD presents object storage as a block device over NBD, allowing standard ext4 to manage the filesystem and simplifying checkpoints and restores. The result is significantly improved reliability and a much simpler storage architecture.

DEPTH ■■■■■6 min read3 days ago

Sign in to save and rate

05GitHub · architecture

From 2,500 requests to 24: Rebuilding star history without the stargazers

GitHub faced abuse and performance issues because tools were scraping user identities to reconstruct repository star history. The engineering team collaborated with maintainers to build a purpose-built aggregate endpoint that returns daily star counts without identities and filters by time before aggregation. This reduced request volume from thousands to a few dozen and eliminated heavy database scans.

DEPTH ■■■■■8 min read11 days ago

Microservices

Sign in to save and rate

06Amazon Web Services · architecture

Multi-region disaster recovery for Amazon API Gateway WebSocket APIs

Real-time applications using WebSocket connections face disruptions during regional AWS outages because connections are tied to specific regions. The team implemented an active-passive multi-region disaster recovery architecture using Route 53 DNS failover, DynamoDB Global Tables, an automated canary health probe, and client-side exponential backoff with jitter. This design automatically detects failures, redirects traffic, and restores client state without manual intervention.

DEPTH ■■■■■10 min read11 days ago

Sign in to save and rate

07Amazon Web Services · architecture

How UTS established a modern curriculum data services foundation on AWS

University of Technology Sydney rearchitected its curriculum data integration using serverless AWS services to decouple systems of record from downstream consumers. By implementing domain-driven design with an event-driven architecture and purpose-built persistence layers, the team achieved zero production incidents, low latency, and reduced operational overhead while managed by a single engineer.

DEPTH ■■■■■9 min read11 days ago

Sign in to save and rate

08Grab · architecture

Powering AI-led research through simulation

The engineering team built a self-contained simulation platform called sim-rs to model marketplace dispatch dynamics and accelerate experimentation. By connecting automated software agents to this simulator with strict safety safeguards, the team successfully optimized strategy policies and simulator performance. This closed-loop lab environment allows agents to test ideas rapidly while ensuring that only valid, production-ready improvements are produced.

DEPTH ■■■■■10 min read2 weeks ago

Machine Learning

Sign in to save and rate

09Amazon Web Services · tooling

Scope workloads and share resilience policies with AWS Resilience Hub

Engineering teams often struggle to scope workloads and maintain up-to-date resilience policies in shared Kubernetes clusters after migrations or deployments. AWS Resilience Hub introduced features enabling Kubernetes label-based resource scoping, generative AI-powered dependency insights, and cross-account resilience policy sharing via AWS Organizations. These capabilities allow teams to isolate specific workloads, prioritize dependency investigations, and enforce centralized recovery standards.

DEPTH ■■■■■14 min read12 days ago

Sign in to save and rate

10GitHub · architecture

Building Git infrastructure for agent-scale development

GitHub is redesigning its Git infrastructure to handle the massive surge in concurrent read and write operations driven by agentic software development and high-volume workloads. The team is decoupling storage from compute by leveraging Azure Blob Storage for durability and lightweight compute workers for requests, which separates scaling dimensions. In internal benchmarks, this approach achieves up to 35 times higher write throughput and independent read scalability.

DEPTH ■■■■■9 min read2 weeks ago

Infrastructure

Sign in to save and rate

11Amazon Web Services · architecture

Stopping business email compromise with AI-driven email security: How VIPRE protects modern enterprises on AWS

VIPRE developed an AI-driven, cloud-native email security solution on AWS to protect enterprises against business email compromise and advanced phishing attacks. The system uses layered machine learning, semantic analysis, and dynamic sandboxing orchestrated via serverless containers and message queues to evaluate over half a million messages daily. In production testing, the architecture successfully identified thousands of BEC attempts while maintaining low-latency processing and reducing administrative overhead.

DEPTH ■■■■■12 min read12 days ago

Sign in to save and rate

12GitHub · architecture

Staying Evergreen: How we automated secure access and repo hygiene in a shared org

Manual repository housekeeping and access reviews for outside collaborators become difficult to maintain as organizations scale. The team built Evergreen, a GitHub App that automates quarterly access reviews and stale repository archiving using native platform features and IssueOps. This automation successfully enforces secure defaults by revoking unanswered access while maintaining a full audit trail in git history.

DEPTH ■■■■■8 min read10 days ago

Sign in to save and rate

13Amazon Web Services · architecture

Bulk Executor for Amazon DynamoDB, Part 2: Lessons we learned the hard way

Engineering a bulk execution tool for Amazon DynamoDB using AWS Glue required addressing several architectural challenges, including cost estimation, graceful job termination, and error handling across hundreds of parallel workers. The team overcame limitations in CloudWatch logging and the Spark connector by combining serverless execution with direct API calls and distributed rate limiting. As a result, the tool provides a scalable, script-like interface for managing large-scale table operations safely.

DEPTH ■■■■■14 min read12 days ago

Sign in to save and rate

14Amazon Web Services · architecture

Agentic antimicrobial resistance surveillance with AWS HealthOmics and Amazon Bedrock AgentCore

Processing public bacterial sequencing data for antimicrobial resistance surveillance typically requires specialized bioinformatics and SQL skills. To streamline this process, the team built a reference architecture using AWS HealthOmics, Amazon S3 Tables, and an Amazon Bedrock AgentCore conversational agent that ingests raw reads, normalizes findings, and answers plain-language questions with cited evidence. The resulting system automates the path from public accession numbers to natural-language epidemiological answers.

DEPTH ■■■■■10 min read13 days ago

Sign in to save and rate

15GitHub · migration

Improving site performance by shipping more CSS

GitHub faced performance degradation on server-side rendering and initial page loads due to scaling issues with its CSS-in-JS solution. The engineering team executed a multi-year migration to CSS Modules and eliminated dynamic styling props using incremental rollouts, wrapper components, and automation tools. This resulted in significant performance gains, including 55% faster server-side rendering and the complete removal of styled-components.

DEPTH ■■■■■8 min read4 weeks ago

FrontendPerformance

Sign in to save and rate

16Grab · architecture

Smarter personalization: How property data helps us understand user price sensitivity

Existing user personalization systems fail to systematically account for residential property values, leading to one-dimensional profiles and regional blind spots. A conceptual four-step method is proposed that combines public property data, large language models, building-level price estimation, and hierarchical clustering to classify user affluence. The approach remains unimplemented, with future viability depending on technical validation, data quality, and privacy approvals.

DEPTH ■■■■■4 min read2 weeks ago

Data EngineeringMachine Learning

Sign in to save and rate

17GitHub · architecture

Rendering huge pull requests in the GitHub Copilot app

Rendering extremely large pull requests with millions of lines and hundreds of comments requires separating deterministic code row geometry from unpredictable dynamic comment blocks. The team implemented an idle-gated measurement scheduler, separate height indices, and identity-based scroll anchoring to maintain smooth scrolling. As a result, the pull request view remains performant and responsive even under extreme loads.

DEPTH ■■■■■14 min read4 weeks ago

Sign in to save and rate

18Amazon Web Services · tutorial

Deploy Oracle Database step by step on Amazon EVS with FSx for ONTAP

This post provides a step-by-step guide to deploying Oracle Database 19c on Amazon Elastic VMware Service using Amazon FSx for NetApp ONTAP as an NFS datastore. It covers provisioning storage, mounting datastores, installing Oracle, configuring SnapMirror for cross-region disaster recovery, and outlining four migration paths. The result is a fully functional enterprise database deployment that preserves existing operational workflows.

DEPTH ■■■■■11 min read3 weeks ago

Sign in to save and rate

19Amazon Web Services · architecture

Architect highly available Oracle Database on Amazon EVS and FSx for ONTAP

Enterprises migrating Oracle databases to Amazon Elastic VMware Service face challenges with storage latency, disaster recovery, and operational consistency. The team designed a highly available architecture combining Amazon EVS bare metal instances with Amazon FSx for NetApp ONTAP NFS datastores and cross-region SnapMirror replication. The resulting setup delivers sub-millisecond storage latency, preserved VMware operational workflows, and robust disaster recovery capabilities.

DEPTH ■■■■■12 min read3 weeks ago

Sign in to save and rate

20Grab · architecture

Data Mesh at Grab (Part III): Operationalizing data reliability with automated DPIs

Grab addressed runtime data reliability issues in its data mesh by implementing automated Data Production Issues (DPIs). The system uses an incident orchestrator to detect contract breaches, a Data Health API for cross-platform root cause analysis, and Hugo for automated remediation. This approach resolved 86.9 percent of incidents automatically and made mean time to resolve six times faster.

DEPTH ■■■■■12 min read8 weeks ago

DatabasesObservability

Sign in to save and rate