AWS NewsDropbox EngineeringGitHub BlogGoogle DevelopersMeta EngineeringNetflix TechBlogStripe Engineering

Total Articles: 19 from 7 sources


AWS News

1. AWS Glue 6.0 now available with 30% lower price and full Apache Iceberg v3 support

URL: https://aws.amazon.com/blogs/aws/aws-glue-6-0-now-available-with-30-lower-price-and-full-apache-iceberg-v3-support/

Published: 2026-08-21 18:53

Summary:

AWS Glue 6.0 is built on a fully modernized runtime, Apache Spark 4.1, Python 3.13, and Scala 2.13, delivering 30% lower pricing than previous AWS Glue versions.


2. In the works: AWS Builder Lofts in Berlin, Hyderabad, and São Paulo

URL: https://aws.amazon.com/blogs/aws/in-the-works-aws-builder-lofts-in-berlin-hyderabad-and-sao-paulo/

Published: 2026-08-18 13:58

Summary:

Each location will be a permanent community space to offer free workshops, networking events, pitch nights, content creation spaces, collaboration/co-working areas, and event hosting for developers, students, or tech professionals who want to walk through the doors.


3. AWS Weekly Roundup: EC2 application status checks, IAM role manager, OpenAI Daybreak on Bedrock, and more (August 17, 2026)

URL: https://aws.amazon.com/blogs/aws/aws-weekly-roundup-ec2-application-status-checks-iam-role-manager-openai-daybreak-on-bedrock-and-more-august-17-2026/

Published: 2026-08-17 16:02

Summary:

Last week, AWS contributors joined the OpenSearch and Valkey communities at Open Source Summit Korea 2026 and MCP DevSummit Seoul 2026 to meet open source developers and contributors At the four-day event, community leaders and users of these Linux Foundation open source projects gathered to share knowledge, collaborate on solutions, and push the projects forward. […]

Dropbox Engineering

1. Improving infrastructure efficiency for growing demand in the age of AI

URL: https://dropbox.tech/infrastructure/improving-infrastructure-efficiency-for-growing-demand-in-the-age-of-ai

Published: 2026-08-18 17:00

Summary:

As demand for AI continues to grow, so does the infrastructure needed to support it.

GitHub Blog

1. The August 17 outage, and the work ahead

URL: https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/

Published: 2026-08-20 18:36

Summary:

An update on the August 17 outage and the steps we’re taking to improve reliability The post The August 17 outage, and the work ahead appeared first on The GitHub Blog.


2. GitHub Copilot app for Beginners: Managing your work

URL: https://github.blog/ai-and-ml/github-copilot/github-copilot-app-for-beginners-managing-your-work/

Published: 2026-08-19 17:50

Summary:

If you’re juggling multiple Copilot sessions, use the My work pane to track what’s in flight, what’s done, and what’s next The post GitHub Copilot app for Beginners: Managing your work appeared first on The GitHub Blog.


3. How canvases make agentic workflows visible, steerable, and cost-efficient

URL: https://github.blog/ai-and-ml/github-copilot/how-canvases-make-agentic-workflows-visible-steerable-and-cost-efficient/

Published: 2026-08-17 16:00

Summary:

Chat is great for intent, but agent work gets lost in the scroll Here is how I use canvases with my agentic workflows—and why your workflow also deserves a canvas The post How canvases make agentic workflows visible, steerable, and cost-efficient appeared first on The GitHub Blog.

Google Developers

1. LiteRT.js, Google’s high performance Web AI Inference

URL: https://developers.googleblog.com/litertjs-googles-high-performance-web-ai-inference/

Published: 2026-08-24 09:42

Summary:

We’re excited to introduce LiteRT.js, the newest member of the LiteRT family Built for JavaScript developers, LiteRT.js delivers state-of-the-art ML model inference performance on WebGPU and upcoming WebNN, with a fallback to WebAssembly for CPU This post provides a quick tour of LiteRT.js and gives web developers everything they need to get started.


2. Systems Engineering Playbook: Optimizing Qwen 3.5-397B MoE on Ironwood (TPU7x)

URL: https://developers.googleblog.com/systems-engineering-playbook-optimizing-qwen-35-397b-moe-on-ironwood-tpu7x/

Published: 2026-08-24 09:42

Summary:

To serve the 397B-parameter Qwen 3.5 Mixture-of-Experts (MoE) model on Ironwood TPUs, engineers developed a modular JAX/Pallas optimization stack that achieved up to a 4.7x inference speedup for prefill-heavy workloads The team bypassed severe hardware sharding constraints by deploying a hybrid Data Parallelism and Expert Parallelism (DP+EP) topology, paired with custom low-level communication fusions like a hierarchical reduce-scatter to optimize cross-device token routing Finally, by executing hardware-aware custom kernels—such as Batched Ragged Page Attention and a fully-fused Gated DeltaNet (GDN) block—they successfully saturated HBM bandwidth and TensorCore MXUs to push system throughput near its theoretical roofline limits.


URL: https://developers.googleblog.com/expanding-choice-in-gemini-enterprise-agent-platform-introducing-grounding-with-parallel-web-search/

Published: 2026-08-24 09:42

Summary:

Google Cloud has partnered with Parallel Web Systems to natively integrate Parallel’s search infrastructure as a web grounding provider on the Gemini Enterprise Agent Platform This integration enables developers to anchor their AI agents in verifiable, real-time web results, significantly improving factual accuracy for complex enterprise workflows Additionally, the partnership offers expanded architectural flexibility, allowing users to programmatically extract, permanently cache, and process web data alongside other large language models.

Meta Engineering

1. How We’re Building Scam Alert on WhatsApp With End-to-End Encryption and Verifiability Guarantees

URL: https://engineering.fb.com/2026/08/12/security/how-were-building-scam-alert-whatsapp/

Published: 2026-08-12 13:00

Summary:

WhatsApp is committed to helping people stay safe while protecting the privacy of their messages As scam tactics evolve — from impersonation to social engineering to AI-generated lures — we’re always evolving as well, so that our protections stay ahead of scammers while protecting people’s personal messages with end-to-end encryption The post How We’re Building Scam Alert on WhatsApp With End-to-End Encryption and Verifiability Guarantees appeared first on Engineering at Meta.


2. From User Sequences to Scaling Laws: A Multi-Stage Architecture for Meta’s Ads Ranking

URL: https://engineering.fb.com/2026/08/05/ml-applications/from-user-sequences-to-scaling-laws-a-multi-stage-architecture-for-metas-ads-ranking/

Published: 2026-08-05 19:20

Summary:

Every day, Meta’s recommendation platforms handle billions of user interactions, generating rich temporal signals that capture individual preferences and intent across products, ads, and content In our 2024 post on sequence learning for ads recommendations, we showed how modeling the order and timing of user actions (rather than relying on static, manually engineered sparse features) […] Read More The post From User Sequences to Scaling Laws: A Multi-Stage Architecture for Meta’s Ads Ranking appeared first on Engineering at Meta.


3. GEM Training: How Meta Doubled the Efficiency of Its LLM-Scale Ads Foundation Model

URL: https://engineering.fb.com/2026/08/03/ml-applications/training-gem-at-llm-scale-meta-ads-recommendation-foundation-model/

Published: 2026-08-03 18:00

Summary:

Meta’s Generative Ads Recommendation Model (GEM), the foundation model behind ads recommendations across Instagram and Facebook, now trains at LLM scale on several thousand of the latest-generation GPUs This post goes into the details on how we achieved: doubling end-to-end (E2E) training efficiency to 20–25% Model FLOPs Utilization (MFU) while scaling training FLOPs 4x in […] Read More The post GEM Training: How Meta Doubled the Efficiency of Its LLM-Scale Ads Foundation Model appeared first on Engineering at Meta.

Netflix TechBlog

URL: https://netflixtechblog.com/a-tale-of-two-flink-autoscalers-e9f6a1b1492b?source=rss----2615bd06b42e---4

Published: 2026-08-21 16:01

Summary:

Each autoscaler node handled the metrics for a subset of Flink jobs, and we never had to write custom sharding or coordination logic to keep up with a growing Flink fleet Starting from the sources, the autoscaler walks the job graph and uses each operator’s TPR, its input/output ratios, and a target utilization to compute the parallelism every vertex needs so that no operator becomes the bottleneck, rather than resizing the whole cluster as a unit.Figure 2: Flink job DAG: current → desired parallelism per vertex, based on busynessThe two approaches make a different contract, summarized below.Table 1: Comparison of the two Flink autoscalersThe decisive difference for us is the last two rows: the OSS autoscaler can scale exactly the stateful, multi-operator jobs our homegrown system could not, and it lets each job carry its own configuration — stabilization periods, thresholds, and other scaling behavior tuned to the workload Having started supporting Flink 2.2 at Netflix, we plan on experimenting with this new state backend to see if it can help eliminate state recovery bottlenecks when scaling large stateful jobs.Looking ahead, we aim to migrate all internal scaler use cases onto the new one based on OSS autoscaler to simplify our operational surface area.Key TakeawaysAlong the way, three lessons that generalize beyond Flink:Metric choice matters more than algorithm sophistication


2. How and Why Netflix Built a Real-Time Distributed Graph: Part 3 — Querying the graph with gRPC…

URL: https://netflixtechblog.com/how-and-why-netflix-built-a-real-time-distributed-graph-part-3-querying-the-graph-with-grpc-0f3468349607?source=rss----2615bd06b42e---4

Published: 2026-08-07 16:01

Summary:

It batches requests, runs them in parallel with graph data assembly, and degrades gracefully when an enrichment source is unavailable.When a client sends a query, the request flows through these layers in sequence: the Query Service parses the request into an execution plan, the execution engine walks the graph level by level through the Storage Abstraction Layer, and if enrichments are requested, the Enrichment Layer fetches and merges external data before the response is serialized back to the client.Now, with that mental model in place, let’s follow a query through this system and see how these choices play out in practice.Executing Queries Efficiently: Following a Query’s JourneyTo see how the RDG query layer works in practice, let’s follow a single query end-to-end and focus on one question: how do we make every step fast?We’ll reuse the deep-narrow example from above:For Account X, show me the Stranger Things viewing history across all profiles: which profiles watched it, what they watched, and when.In graph terms, this becomes a 2‑hop traversal:Account X → has_profile → ProfilesProfiles → started_watching → Content (filtered for “Stranger Things”)We’ll walk through how this query moves through the layers we described above:Reading and interpreting the requestReading from storage efficientlyExecuting traversal with breadth‑first levelsRunning many operations in parallel, but safelyFiltering smartly to keep only what mattersMaking repeat queries faster with cachingBy the end, we’ll see how a 2-hop query like our Stranger Things example, with streaming, filtering, and parallel execution, can complete in under 100ms.Step 1: Reading the Request: Deciding What the Query Really WantsEvery query starts as a gRPC request The query was:For Account X, show me the Stranger Things viewing history across all profiles: which profiles watched it, what they watched, and whenSo we still need to fetch each profile’s history and filter it down to Stranger Things sessions That’s why our Stranger Things query completes in under 100ms.Step 4: Parallel Execution: Doing Many Things at Once, SafelyBreadth-first traversal enables parallel work at each level, which is the key to low latency.At Level 2 of our Stranger Things query, we fetch started_watching edges for each profile


3. Modeling Device Capabilities for Analytics

URL: https://netflixtechblog.com/modeling-device-capabilities-for-analytics-e7607acebde8?source=rss----2615bd06b42e---4

Published: 2026-07-31 16:01

Summary:

To ensure the best possible user experience, we rely on a deep understanding of device capabilities We use a cumulative table to process information about the device’s capabilities By relying on data-driven insights, we can make informed decisions about which features to enable on specific devices, ensuring both performance and reliability.Modeling Device Capabilities for Analytics was originally published in Netflix TechBlog on Medium, where people are continuing the conversation by highlighting and responding to this story.

Stripe Engineering

1. Why global workers are driving demand for stablecoin payouts

URL: https://stripe.com/blog/why-global-workers-are-driving-demand-for-stablecoin-payouts

Published: 2026-08-19 00:00

Summary:

Platforms like DoorDash, Meta, and Deel already enable stablecoin payouts for global workers We surveyed 2,300 workers in 20 countries to see what’s driving stablecoin demand, where the opportunity is highest, and how other platforms can adapt.


2. New currency capabilities for global businesses to cut FX costs

URL: https://stripe.com/blog/reduce-fx-costs-with-stripe

Published: 2026-08-17 00:00

Summary:

Two product upgrades make it easy for global businesses to manage FX entirely on Stripe We’re expanding multicurrency settlement to more markets and currencies, and we’re introducing the ability to convert currencies instantly—all on Stripe.


3. Mapping the AI economy

URL: https://stripe.com/blog/mapping-the-ai-economy

Published: 2026-08-11 00:00

Summary:

AI companies are undergoing rapid global expansion while achieving unprecedented rates of growth We analyzed Stripe data to understand where global demand is the strongest, and how companies can build to best capture that demand.


Generated on 2026-08-24 09:42:58