AWS NewsDropbox EngineeringGitHub BlogGoogle DevelopersMeta EngineeringNetflix TechBlogStripe Engineering

Total Articles: 20 from 7 sources


AWS News

1. Get started with OpenAI GPT-5.5, GPT-5.4 models, and Codex on Amazon Bedrock

URL: https://aws.amazon.com/blogs/aws/get-started-with-openai-gpt-5-5-gpt-5-4-models-and-codex-on-amazon-bedrock/

Published: 2026-06-01 21:33

Summary:

OpenAI frontier models GPT-5.5 and GPT-5.4, and Codex, the OpenAI coding agent, are now generally available on Amazon Bedrock Deploy frontier models on Bedrock’s high performance inference engine with built-in security, governance, and pay-per-token pricing.


2. AWS Weekly Roundup: Claude Opus 4.8 on AWS, Aurora MySQL with Kiro Powers, and more (June 1, 2026)

URL: https://aws.amazon.com/blogs/aws/aws-weekly-roundup-claude-opus-4-8-on-aws-aurora-mysql-with-kiro-powers-and-more-june-1-2026/

Published: 2026-06-01 14:25

Summary:

In my last Week in Review post, I shared what I’d been hearing from customers in the AI-Driven Development Lifecycle (AI-DLC) workshops I’ve been delivering Last week I was back at it, this time in Denver for a two-day AI-DLC workshop, where I helped facilitate 17 teams to deliver nearly 20 separate use cases in […]


3. Introducing the next generation of AWS Resilience Hub for generative AI-based SRE resilience journey

URL: https://aws.amazon.com/blogs/aws/introducing-the-next-generation-of-aws-resilience-hub-for-generative-ai-based-sre-resilience-journey/

Published: 2026-05-28 19:29

Summary:

AWS launches the next generation of AWS Resilience Hub with a significantly expanded experience that brings together a new application model, dependency discovery assessment, generative AI-powered failure mode analysis, modular resilience policies, and organization-wide reporting.

Dropbox Engineering

1. Beyond code generation: rethinking engineering productivity in the age of AI agents

URL: https://dropbox.tech/culture/beyond-code-generation-rethinking-engineering-productivity-in-the-age-of-ai-agents

Published: 2026-05-28 18:00

Summary:

How Dropbox is moving from AI tools that assist engineers to agentic systems that can execute scoped tasks, and how we’re building platforms to support those workflows.


2. Introducing Nova, our internal platform for coding agents

URL: https://dropbox.tech/machine-learning/introducing-nova-our-internal-platform-for-coding-agents

Published: 2026-05-21 16:00

Summary:

Nova lets engineers run multiple coding sessions in parallel and lets internal systems use AI agents as part of automated workflows.

GitHub Blog

1. GitHub Copilot app: The agent-native desktop experience

URL: https://github.blog/news-insights/product-news/github-copilot-app-the-agent-native-desktop-experience/

Published: 2026-06-02 17:30

Summary:

At Microsoft Build 2026, GitHub introduced new tools, updates, and surfaces so agents can work the way you already work The post GitHub Copilot app: The agent-native desktop experience appeared first on The GitHub Blog.


2. Still a developer. Just outside. Our latest GitHub Shop collection is here.

URL: https://github.blog/news-insights/company-news/still-a-developer-just-outside-our-latest-github-shop-collection-is-here/

Published: 2026-05-28 18:18

Summary:

The ESC collection lets you escape the confines of your desk and get out into the sun where good ideas are bound to happen The post Still a developer Our latest GitHub Shop collection is here. appeared first on The GitHub Blog.


3. GitHub for Beginners: Getting started with Git and GitHub in VS Code

URL: https://github.blog/developer-skills/github/github-for-beginners-getting-started-with-git-and-github-in-vs-code/

Published: 2026-05-25 16:00

Summary:

Discover how to use VS Code to interact with GitHub and maintain your projects The post GitHub for Beginners: Getting started with Git and GitHub in VS Code appeared first on The GitHub Blog.

Google Developers

1. Agents CLI in Agent Platform: create to production in one CLI

URL: https://developers.googleblog.com/agents-cli-in-agent-platform-create-to-production-in-one-cli/

Published: 2026-06-03 13:14

Summary:

Google Cloud has introduced the Agents CLI, a specialized tool designed to bridge the gap between local development and production-grade AI agent deployment The CLI provides coding assistants with machine-readable access to the full Google Cloud stack, reducing context overload and token waste during the scaffolding process By streamlining evaluation, infrastructure provisioning, and deployment into a single programmatic backbone, the tool enables developers to move from initial concept to a live service in hours rather than weeks.


2. Building real-world on-device AI with LiteRT and NPU

URL: https://developers.googleblog.com/building-real-world-on-device-ai-with-litert-and-npu/

Published: 2026-06-03 13:14

Summary:

LiteRT is a production-ready framework designed to help mobile developers unlock the power of Neural Processing Units (NPUs), overcoming the performance and battery limitations of traditional CPU or GPU processing By providing a unified API that abstracts away hardware complexities, it allows industry leaders like Google Meet and Epic Games to deploy sophisticated AI models for real-time video, animation, and speech recognition with significantly higher efficiency The platform further supports developers through benchmarking tools and cross-platform compatibility, enabling seamless AI deployment across mobile devices, AI PCs, and industrial IoT hardware.


3. Speeding Up AI: Bringing Google Colossus to PyTorch via GCSFS and Rapid Bucket

URL: https://developers.googleblog.com/speeding-up-ai-bringing-google-colossus-to-pytorch-via-gcsfs-and-rapid-bucket/

Published: 2026-06-03 13:14

Summary:

Google Cloud has introduced a high-performance integration that connects Rapid Storage directly to PyTorch via the fsspec interface to eliminate AI training bottlenecks By utilizing Google’s Colossus architecture and bidirectional gRPC streaming, the solution offers up to 15 TiB/s aggregate throughput and significant reductions in latency These improvements allow developers to speed up total training time by 23% with zero code changes required beyond updating the storage bucket type.

Meta Engineering

1. SilverTorch: Index as Model — A New Retrieval Paradigm for Recommendation Systems

URL: https://engineering.fb.com/2026/05/26/ml-applications/silvertorch-index-as-model-new-retrieval-paradigm-recommendation-systems/

Published: 2026-05-26 16:00

Summary:

We’re introducing SilverTorch, a reimagining of recommendation systems that unifies all retrieval components for user generated content under a unified architecture Our research paper, “SilverTorch: A […] Read More The post SilverTorch: Index as Model — A New Retrieval Paradigm for Recommendation Systems appeared first on Engineering at Meta.


2. Reel Friends: Building Social Discovery that Scales to Billions

URL: https://engineering.fb.com/2026/05/13/ml-applications/reel-friends-building-social-discovery-that-scales-to-billions/

Published: 2026-05-13 13:00

Summary:

It highlights Reels your friends have watched and reacted to But sometimes the features that seem the most straightforward require the deepest engineering work The post Reel Friends: Building Social Discovery that Scales to Billions appeared first on Engineering at Meta.


3. Migrating Data Ingestion Systems at Meta Scale

URL: https://engineering.fb.com/2026/05/12/data-infrastructure/migrating-data-ingestion-systems-at-meta-scale/

Published: 2026-05-12 16:00

Summary:

Meta’s data ingestion system, which our engineering teams leverage for up-to-date snapshots of the social graph, has recently undergone a significant revamp to enhance its reliability at scale Moving from our legacy system to our new architecture required a large-scale migration of our entire data ingestion system The post Migrating Data Ingestion Systems at Meta Scale appeared first on Engineering at Meta.

Netflix TechBlog

1. Dynamically Splitting Wide Partitions in Cassandra for Time Series Workloads

URL: https://netflixtechblog.com/dynamically-splitting-wide-partitions-in-cassandra-for-time-series-workloads-0eded064f456?source=rss----2615bd06b42e---4

Published: 2026-06-03 02:05

Summary:

Using these tools, we can detect cases of both over and under partitioning.Below is an example of over‑partitioning, where the TimeSeries provisioning pipeline selected very small time_bucket intervals based on user provided inputs:Provisioning selected 60s time buckets based on user inputscausing partitions to have less than 10 KB of data, leading to high read amplification and thread queueing:Histogram of the given Cassandra table showing partition size percentilesIn order to tune partition strategies efficiently, we added a background worker, which monitors partition histograms of Time Slices attached to a given application, and exposes it via a Cassandra virtual table:Histograms exposed through a Cassandra Virtual tableIt then computes an adjustment factor when it detects partition sizes not meeting a configured density Simply tolerating elevated latencies or timeouts when querying these IDs is not a desirable outcome.This is where dynamic partitioning comes into play.Solution 2: Dynamic Partitioning per IDDynamic partitioning is an asynchronous pipeline that auto-detects and splits wide partitions on a TimeSeries ID level rather than at the table level.It has three main stages:Detection: Detects wide partitions for a given TimeSeries ID during the read path.Planning & Splitting: Plans and executes splits of those partitions into optimal sizes asynchronously.Serving Reads: Re-routes the read queries transparently to read data from the split partitions when ready.This is how it works at a high level; we will dive into details after:Dynamic Wide Partition Split Async PipelineHere are the different stages of the pipeline:DetectionEvery TimeSeries read operation tracks how many bytes are read for a given partition For example, if EventBucketPartitionSplitStrategy is selected, we split the partition by assigning more event buckets to the same time bucket


2. High-Throughput Graph Abstraction at Netflix: Part I

URL: https://netflixtechblog.com/high-throughput-graph-abstraction-at-netflix-part-i-e88063e6f6d5?source=rss----2615bd06b42e---4

Published: 2026-05-29 18:49

Summary:

Looking ahead, we plan to leverage the graph schema for additional improvements, such as:Minimizing Query Fanout: By using edge cardinality within edge mappings, we aim to select the most efficient traversal paths and minimize query fanout.Improved Developer Experience: The schema will support generating a type-safe data access layer and enhance the Gremlin-like API with schema awareness.Next, let’s look at how this data is organized in a real-time index within the KV Abstraction.Real-Time Index: Key-Value StorageBefore we discuss how the data is organized into graph indexes, let’s discuss how KV organizes data within namespaces and provides idempotency guarantees:Data partitioning: A namespace is associated with a table in the underlying storage layer In order to ensure optimal performance without exerting too much memory pressure, we aim to limit the number of edges per source node within the system.Next, let’s explore the caching strategies used by the Abstraction.Caching Strategies in Graph AbstractionAlthough the Graph Abstraction already provides efficient reads and writes to durable storage, caching remains critical for the stability and performance of any graph datastore for two key reasons:Write amplification: A single write on the fronting service can result in multiple writes to the backing durable storage due to the use of multiple indexes As illustrated in the diagram below, both the caching layer and durable storage replicate data asynchronously across regions, resulting in an eventually consistent system.Now that we’ve covered storing the real-time graph index, let’s see how it enables graph traversals.Graph TraversalsThe Abstraction provides a custom gRPC traversal API, inspired by Gremlin, which enables exploration of the distributed graph by letting users chain traversals, apply filter criteria, sort results, limit results, and more.Let’s explore a hypothetical scenario where the Abstraction is used to recommend shows to users on a shared device, by considering the duration of the most recent viewing session for each show across all profiles and accounts associated with that device:TraversalRequest.newBuilder() .setNamespace("") .setTraversalQuery( TraversalQuery.newBuilder() // Given id of the ‘device’ node type. .setStartNode(node(“device”, “my-device-id”)) .setTraversal( Traversal.newBuilder() // fetch the first 5 connections .setEdgeLimit(5) .setDirectionTraversal( DirectionTraversal.newBuilder() // traverse in the IN direction .setDirection(IN) // minimize data exchange: only interested in certain properties .addNodePropertiesSelections(propSelection(“account”, “created_at”)) .addNodePropertiesSelections(propSelection(“profile”, “last_active”)) .setDirectionFilter( DirectionFilter.newBuilder() // only interested in certain connected types .setTypeMatchingStrategy(EXCLUDE_NON_TARGETED) .addAllNodeFilters(typeFilters(“account”, “profile”)))) // chain traversals to the intermediate result .addNextTraversals( Traversal.newBuilder() .setOrder(LATEST) // limit to 200 connections for the 2nd hop .setEdgeLimit(200) .setDirectionTraversal( DirectionTraversal.newBuilder() // now traverse in the OUT direction .setDirection(OUT) .addEdgePropertiesSelections(propSelection(“watched”, “view_time”)) .addEdgePropertiesSelections(propSelection(“has_plan”, “active”)) .setDirectionFilter( DirectionFilter.newBuilder() .setTypeMatchingStrategy(EXCLUDE_NON_TARGETED) .addAllNodeFilters(typeFilters(“title”, “plan”))))))) .build();And let’s visualize the intended results set produced by the request above:We’ll explore the design and implementation of traversal planning and execution, along with different traversal types, in the Part II of this blog series.Now let’s look at the performance metrics of Graph Abstraction based on current production use cases.Real World PerformanceAcross all applications at Netflix, Graph Abstraction ensures high availability while processing up to 10 million operations per second across all writes, individual edge / node reads and traversals at peak hours:Edge and node persistence achieve single-digit millisecond latencies (p99 shown in red, p90 shown in orange, and p50 shown in green):Traversal performance depends on the number of hops, the edge fanout at each stage, and associated filters and sort orders


3. From Silos to Service Topology: Why Netflix Built a Real-Time Service Map

URL: https://netflixtechblog.com/from-silos-to-service-topology-why-netflix-built-a-real-time-service-map-0165ba13a7bc?source=rss----2615bd06b42e---4

Published: 2026-05-29 14:01

Summary:

We needed to combine multiple sources.These lessons shaped every decision we made in building Service Topology.What We Needed: A Living MapWe set out to build something specific: a living map of our infrastructure — one that updates in real-time as services deploy, as traffic patterns shift, as new dependencies form and old ones disappear.The requirements were clear:Real-time updates, not stale snapshots: In an environment where services deploy continuously, yesterday’s topology map is archaeology, not observability.Fast queries at scale: When an engineer is troubleshooting at 3am, they can’t wait minutes for a query to return This graduated approach also prevents hot spots by distributing load across multiple points even when specific applications or network intermediaries see 100x more traffic than others.Graph Storage: We persist the topology in Netflix’s graph database, an abstraction layer built on top of our distributed key-value storage infrastructure Each of our three data sources (network flows, IPC metrics, tracing) creates a separate graph that can be queried independently or merged.gRPC API: We expose the topology through a gRPC service that supports multi-hop traversal, filtering by availability tier and business domain, pagination for large result sets, and sub-second query response times.The technical details of building this at Netflix scale — handling Kafka lag, managing memory and garbage collection, optimizing distributed processing, debugging reactive streams — deserve their own discussion

Stripe Engineering

1. Solo founding is at an all-time high: Top performers have these traits in common

URL: https://stripe.com/blog/top-solo-founder-traits

Published: 2026-05-28 00:00

Summary:

In 2025, solo founders in the top decile generated 61 times the revenue of the median solo founder in their first six months We analyzed the data to understand what drives that gap.


2. Expanding Stripe Radar to protect more of your business

URL: https://stripe.com/blog/expanding-stripe-radar-to-protect-more-of-your-business

Published: 2026-05-27 00:00

Summary:

Radar now blocks high-risk transactions across all supported payment methods; defends against new fraud types like multi-account abuse and pay-as-you-go abuse, regardless of which payment processor you use; and gives platforms new tools to evaluate and mitigate merchant risk on and off Stripe.


3. Five vertical SaaS insights from Sessions 2026

URL: https://stripe.com/blog/vertical-saas-insights-sessions-2026

Published: 2026-05-11 00:00

Summary:

AI is forcing platforms to expand beyond pure software See how vertical SaaS platforms are using payments, financial services, and agentic commerce to build more durable businesses.


Generated on 2026-06-03 13:14:34