Archives
-
Explore agentic AI with ServiceNow and New Relic
New Relic
Let's talk about agentic AI. Join us at New Relic Now on 25 June at 9am BST / 10am CEST for a fireside chat with ServiceNow's VP of Product, ITOM—Gabby Menachem, where we'll discuss the pioneering power of Intelligent Observability combined with agentic actions.RSVP Now 
Featured Speakers
Gabby Menachem, VP of Product, ITOM at ServiceNow: Learn how integrating observability insights with ServiceNow streamlines customer support and automates critical business-impact analyses. Gain insights into leveraging agentic AI for truly transformative efficiency.
Thomas Lloyd, Chief Business & Operations Officer at New Relic: Explore how New Relic’s platform turns data into actionable intelligence, optimising operations and enhancing your team’s ability to predict and prevent service disruptions.
Secure your spot to hear directly from industry leaders at the forefront of AI integration.
Register Now
by "New Relic Events" <emeamarketing@newrelic.com> - 05:05 - 29 May 2025 -
What it takes for the creative process to thrive
On McKinsey Perspectives
Brought to you by Alex Panas, global leader of industries, & Axel Karlsson, global leader of functional practices and growth platforms
Welcome to the latest edition of Only McKinsey Perspectives. We hope you find our insights useful. Let us know what you think at Alex_Panas@McKinsey.com and Axel_Karlsson@McKinsey.com.
—Alex and Axel
—Edited by Belinda Yu, editor, Atlanta
This email contains information about McKinsey's research, insights, services, or events. By opening our emails or clicking on links, you agree to our use of cookies and web tracking technology. For more information on how we use and protect your information, please review our privacy policy.
You received this email because you subscribed to the Only McKinsey Perspectives newsletter, formerly known as Only McKinsey.
Copyright © 2025 | McKinsey & Company, 3 World Trade Center, 175 Greenwich Street, New York, NY 10007
by "Only McKinsey Perspectives" <publishing@email.mckinsey.com> - 01:28 - 29 May 2025 -
Webinar: SAP Business Suite for business leaders
SAP Business Suite: Connected business decisions
Uncertainty isn’t new—but the pace and complexity of change are accelerating. Across industries, business leaders are being asked to do more with less, while still staying focused on long-term growth and stability.
Join us for our June 24 webinar to explore how SAP Business Suite supports this balance—by helping organizations unify applications, data, and AI to improve visibility, simplify decisions, and respond with greater agility. You’ll hear from SAP experts and customers as they share how they’re navigating today’s realities while preparing for what’s next.
We’ll explore:
- How to connect strategy, data, and operations across your business
- Customer stories from organizations leading through transformation.
- AI and automation that deliver real-time, business-wide insights.
- Key integration benefits for CIOs, CEOs, and cross-functional leaders.
- What’s included in the new SAP Cloud Private Base and Premium packages.
SAP Business Suite
SAP core applications, data, and AI come together—powered by SAP Business Technology Platform—to deliver exceptional business value and help your business stay ready for what’s next.
Learn more
Contact us
See our complete list of local country numbers
SAP (Legal Disclosure | SAP)
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
You are receiving this e-mail for one or more of the following reasons: you are an SAP customer, you were an SAP customer, SAP was asked to contact you by one of your colleagues, you expressed interest in one or more of our products or services, or you participated in or expressed interest to participate in a webinar, seminar, or event. SAP Privacy Statement
This email was sent to info@learn.odoo.com on behalf of the SAP Group with which you have a business relationship. If you would like to have more information about your Data Controller(s) please click here to contact webmaster@sap.com.
This offer is extended to you under the condition that your acceptance does not violate any applicable laws or policies within your organization. If you are unsure of whether your acceptance may violate any such laws or policies, we strongly encourage you to seek advice from your ethics or compliance official. For organizations that are unable to accept all or a portion of this complimentary offer and would like to pay for their own expenses, upon request, SAP will provide a reasonable market value and an invoice or other suitable payment process.
This e-mail was sent to info@learn.odoo.com by SAP and provides information on SAP’s products and services that may be of interest to you. If you received this e-mail in error, or if you no longer wish to receive communications from the SAP Group of companies, you can unsubscribe here.
To ensure you continue to receive SAP related information properly, please add sap@mailsap.com to your address book or safe senders list.
by "SAP" <sap@mailsap.com> - 09:32 - 28 May 2025 -
Everyone’s Talking About AI, But Who’s Actually Getting It Right?
Everyone’s Talking About AI, But Who’s Actually Getting It Right?
Hi MD Abul,
Hope you had a great Memorial Day weekend!
If your LinkedIn feed is anything like mine, it’s overflowing with bold claims about how AI is changing everything, transforming industries, and solving every business problem under the sun.
But here’s the reality we’re seeing on the ground: most organizations still don’t know what to do with AI. They're either overwhelmed, underprepared, or chasing shiny tools without a strategy. And without clean data, clear governance, and business alignment, even the best AI initiatives fizzle out.
That’s where the real opportunity lies: not just using AI, but using it wisely to streamline operations, enable better decision-making, and drive real transformation.
And that’s exactly what we’ll be unpacking at this year’s Digital Stratosphere conference.
We’re bringing together independent experts, thought leaders, and real-world transformation stories to cut through the hype and focus on what actually works, with or without AI. If you’re trying to future-proof your business, this is where you’ll want to be.
Digital Stratosphere 2025: Aug 26–28th
Mission: AI-Possible is taking off this August at Digital Stratosphere 2025.
Join us in Denver!Use the code "earlybird" for 20% off your ticket(s)!
Best regards,
Eric Kimberling
by "Eric Kimberling" <eric.kimberling@thirdstage-consulting.com> - 08:32 - 28 May 2025 -
Discover the Future of Wellness with Graphene Technology
Dear Info,
Are you passionate about health and wellness? At YangCare, we’ve combined the wisdom of traditional Chinese medicine with the revolutionary power of graphene, the “king of new materials,” to create innovative health solutions.
Our graphene energy rooms, knee chambers, and suspension moxibustion devices are designed to elevate your wellness journey. Here’s what makes our products unique:
· Single-layer graphene: Transparent, ultra-conductive, and safe, emitting far-infrared rays (6-14μm) that resonate with your body’s natural frequency.
· Negative oxygen ions: Enjoy a refreshing experience with 40,000-50,000 ions/cm³, even at 50°C.
· Natural materials: Crafted from premium cedar wood, toxin-free, and hand-polished for durability and comfort.
Whether you’re an individual seeking natural wellness or a business looking to enhance your offerings, our products provide a perfect blend of tradition and technology. Visit [website] or reply to this email to learn more.
To your health,
YangCare Team
by "Ingraham Hubel" <ingrahamhubel986@gmail.com> - 04:13 - 28 May 2025 -
How Amazon Key Opens 100 Million Doors Every Year
How Amazon Key Opens 100 Million Doors Every Year
Forwarded this email? Subscribe here for moreNote: This article is written in collaboration with the engineering team of Amazon Key. Special thanks to Kaushik Mani (Director at Amazon) and Vijay Nagarajan (Engineering Leader) from Amazon Key for walking us through the architecture and challenges they faced while building this system. All credit for the technical details and diagrams shared in this article goes to the Amazon Key Engineering Team.
Picture a customer buzzing with excitement for their package, only to find a "delivery failed" slip because a locked gate stood in the way.
That’s what Amazon faced in 2018. At the time, delivery delays were frequently caused by delivery associates being unable to enter access-controlled areas in residential and commercial properties, including gated communities, leading to missed deliveries and poor customer experiences.
The access control systems in such areas were never designed to work with modern logistics. Moreover, the hardware systems were wildly fragmented with no common standard. Many of these devices were hardwired into buildings in ways that make network access unreliable or downright impossible.
To bridge this gap, Amazon launched an initiative to address a common but impactful delivery challenge: how to provide drivers with secure access to gated residential and commercial communities and buildings.
The result was Amazon Key: a system that allows verified delivery associates to unlock gates and doors at the right time, with the right permissions, and only for the duration needed to complete a delivery. What started with a small internal team and a few device installations has now grown into a system that unlocks 100 million doors annually, across 10+ countries and 4 continents, with five unlocks every second.
We recently had the wonderful opportunity to sit with Kaushik Mani and Vijay Nagarajan from the Amazon Key team to learn how they built this system and the challenges they faced.
In this article, we are bringing you our findings and what we learned about Amazon’s culture of entrepreneurship that played a key role in making Amazon Key a reality.
The Beginnings
The origins of Amazon Key can be traced back to 2016.
Upon moving to Seattle to work for Amazon, Kaushik noticed a number of underutilized parking spots in buildings. However, technology to open them up to users was lacking. Kaushik worked on his own initiative to solve this problem for a Seattle apartment building. The solution needed to address a highly fragmented category of garage door mechanisms.
Kaushik invented a cloud-connected universal key that worked on any electrically controlled lock. This later became known as Amazon Key. Kaushik deployed it at customer locations to validate the solution. He wrote the business plan around his invention and pitched it to several leaders across Amazon. After 6 months of pitching the idea and receiving several refusals, Kaushik was eventually funded by Marketplace.
He worked on the idea for a year, but unfortunately, no customers signed up. Building owners loved the idea of selling parking but worried about trust and safety aspects of allowing access to anyone. So, in 2018, he pivoted the business case to benefit only last-mile deliveries for building access and launched the first version of Amazon Key with 1 firmware and 1 hardware engineer.
From a stats point of view, Amazon delivery associates deliver over a billion packages annually to tens of millions of customers living in access-restricted apartment buildings in the US, EU, and Japan. Without Amazon Key, a driver must engage with the customer, property manager, or other residents to receive access when faced with an access control barrier. This results in packages not being delivered on time and reliably due to drivers not gaining access to the apartment building/gated communities. One example highlighted by the team involved a customer expecting a cereal delivery at 4 a.m., timed precisely so breakfast could be prepared on schedule. If the delivery associate couldn’t get past a gate, that delivery would fail, turning what should be a seamless experience into a broken promise.
Not having on-demand access to these buildings was a core capability gap, resulting in repeated defects, the impact of which started becoming more pronounced as customer demand and delivery speeds increased. This shifted the idea from “interesting” to “strategic necessity”.
By 2018, Amazon Key entered early-stage operations. The rollout was intentionally conservative, targeting just 100 buildings to start, followed by another 100 shortly after. But even in this narrow scope, the system’s potential became clear.
Still, scaling was far from straightforward. As Kaushik Mani put it brilliantly: "It takes $5 to build the solution, but $95 to make it secure." That ratio became even more daunting in the context of Amazon’s global footprint, where every expansion introduced a new set of hardware, protocols, and deployment challenges.
And that’s where the Amazon Key engineering team came together to build a solution that made this scale possible.
The First Attempt: Serverless
Amazon started where most pragmatic teams start: build the simplest thing that works.
They created a small, Ethernet-connected device that could physically integrate with most ACS (Access-Control System) hardware. When a delivery associate showed up at a gate, they’d tap in the Amazon Flex App, which triggered a cloud command to the device via AWS IoT to open the gate.
See the diagram below that shows this setup:
The system stack looked something like this:
Hardware: A small, Ethernet-connected device installed on-site, physically wired to the building’s existing access control systems. It could trigger unlocks for 95% of gate types.
AWS IoT: Provided secure, two-way communication between the device and the cloud.
AWS Lambda (Java): Handled unlock requests, triggered by delivery associates using the mobile app.
DynamoDB: Stores metadata like device status, gate mappings, and property permissions.
Amazon Flex App: The application delivery associates use to initiate access requests when approaching a gate.
The early design was lean, minimal, and pragmatic. The goal was to give Amazon delivery associates a reliable way to unlock residential gates. This approach worked well for limited properties.
However, as Amazon Key expanded, hundreds of devices became thousands. A few cities became multiple countries. The rapid expansion created issues for the solution’s scalability in different areas:
1 - Device and Infra Challenges
When deploying access devices across thousands of properties, physical installation constraints quickly became a major factor in hardware design.
Space limitations were a frequent issue. Callboxes, where devices were often installed, have very limited internal space. Larger hardware simply could not fit inside these enclosures. Similarly, at common installation points like mail rooms, front doors, or outdoor callboxes, Ethernet connectivity was often unavailable, making it impractical to rely on wired networking as a standard installation requirement. Running new Ethernet cables required drilling through walls, digging up pathways, or convincing building managers to modify shared infrastructure.
Initially, the device supported two relay ports and two Wiegand ports, allowing it to control multiple access points and interact with various types of legacy systems. However, based on field experience, the design was streamlined to one relay and one Wiegand port. This change reduced hardware complexity and footprint, which made installations easier and more reliable.
Over time, the team also decided to stop using the Wiegand interface during installations. The main reason was operational: Wiegand credentials often change periodically, making long-term integration unreliable and harder to maintain without frequent updates.
2 - Serverless Backend with Java Cold Starts
Another problem the team faced was Java-based Lambdas with higher cold start times. It might be fine for a background task, but not when a delivery associate is standing at a gate holding a package to deliver.
Also, the initial backend design used a shared gateway across countries. This meant launching in new regions required coordination with multiple teams, environments, and deployment pipelines.
3 - Field Resilience
The unlock commands were fire-and-forget.
The delivery associates had no feedback. They’d tap “unlock” and hope for the best. If a device was offline, the system didn’t know. Also, the operations team couldn’t see device health or network quality remotely. Troubleshooting meant sending people into the field, which was slow, expensive, and frustrating.
Phase 2: Re-architecting for Scale
The early Lambda-based design was fast to build, but faced issues in terms of scalability. Therefore, the Amazon Key engineering team decided to design the system for a global scale.
Two key changes they made were as follows:
1 - Moving Away from Ethernet
No matter how smart the backend was, if the device couldn’t connect reliably, nothing else mattered. So the hardware team built something better.
They created a new, compact, cellular-enabled device, small enough to install discreetly and robust enough to operate in the field. It had multi-carrier support baked in, spanning 70+ countries, with failover if one network dropped. It removed the earlier dependency on local building infrastructure.
This change shifted the device from “hard to deploy” to “install and forget.” It also gave Amazon a repeatable, global deployment model, which was critical for international rollout.
2 - The Move to Containers
The backend team knew Lambda wasn’t going to cut it anymore: not at this scale
The delivery associates needed real-time unlocks. That meant persistent device connections, low tail latency, and guaranteed CPU availability. Lambda (especially with Java) wasn’t ideal for that. Therefore, they moved to ECS Fargate, Amazon’s container-native compute layer.
So, why was ECS Fargate chosen specifically?
Vijay Nagarajan from the Amazon Key engineering team gave a few important reasons for this choice:
Fargate allows fine-grained control over vCPU and memory settings, which helped the team optimize performance based on real-world load.
Deploying across multiple Availability Zones (AZs) allowed the system to balance cost and availability.
Fargate can scale based on concrete indicators like outstanding request count, memory pressure, or CPU usage.
Compared to running the same workload on EC2, Fargate proved to be more cost-efficient, especially since it avoided the operational burden of managing EC2 instances.
Unlike Lambda, which spins up and tears down execution contexts, Fargate tasks remain provisioned and continuously running, making them well-suited for latency-sensitive workflows like device unlocks
In short, Fargate gave them the control and performance of EC2, without the ops overhead of managing VMs.
The hardest part of this evolution was surgically moving life traffic to the newer services. The team had to create feature flags to support both the flows. This meant that every time they introduced a new service, they had to slowly migrate traffic to the newer service.
To make things clear, Lambda wasn’t completely abandoned. There are still a few use cases that rely on Lambda, such as:
One-time device JITR registration that happens at the factory.
During installation, they also take the image of where the device is installed. The post-processing to scan for malware/size resolution is still a Lambda function.
Benefits
Together, cellular hardware and containerized backend unlocked a new class of capabilities such as:
Faster unlock response times (<1.5s consistently).
Global expansion without localized network constraints.
The ability to handle edge cases gracefully, like intermittent connectivity, retries, and failovers.
It also laid the foundation for the next evolution: breaking the system into modular services, standardizing workflows, and monitoring what matters.
Adopting Microservices
The move to ECS Fargate was also a chance to break apart the system into clean, well-scoped services. Amazon Key went from a collection of Lambda functions to a cohesive service-oriented architecture that could be evolved in the future.
See the diagram below for a high-level view of the system running on ECS Fargate:
This wasn’t microservices for microservices’ sake. Each service took care of a real need. Here are the details of the key services that were a part of the overall architecture:
1 - Provisioning App
This service was developed to simplify the installation process and support onboarding new properties into the Amazon Key backend.
2 - Key Gateway Service
This service handles requests originating from the Flex App when a delivery is scheduled to an Amazon Key-enabled property. It also enabled the system to support international launches by managing region-specific traffic routing.
3 - Access Management Service
This service maintains the relationships between gates, properties, and devices. It also manages mappings with Amazon Logistics and associated job workflows such as installation and maintenance.
4 - Device Management Service
Built on top of AWS IoT, this service provided a wrapper around commands sent to devices. It supported both synchronous and asynchronous APIs and streamed device performance metrics into Redshift for analysis.
5 - AMZL Onboarding Service
This service listens to events from the Access Management Service and onboards properties into the Amazon Logistics system, allowing them to be used in routing and delivery workflows.
6 - OTA Management Service
This service provides pipelines for deploying firmware updates to devices in the field. It supported two modes:
One-time OTA used to test firmware with a small cohort of devices.
Campaign-based OTA, which rolled out updates across device pools grouped by geographical location until all were up to date.
7 - Flex App
The Flex App is used by Amazon delivery associates to complete package deliveries. It integrates with Amazon Key to support access control during deliveries.
8 - Data Lake and Analytics
Metrics from different services are pushed into Redshift for analytics. Dashboards built using AWS QuickSight provide both aggregated summaries and device-level drilldowns.
The Cellular Connectivity Challenge
Switching from Ethernet to cellular connectivity solved key deployment issues but introduced new challenges.
Devices were installed in a variety of environments, such as exposed call boxes outside communities or electrical rooms located deep within buildings, and faced varying connectivity conditions. Cellular performance was inconsistent and location-dependent, often changing throughout the day. These fluctuations impacted the reliability of time-sensitive operations like unlock requests, especially during delivery hours.
To address this, the team developed the Intelligent Connection Manager (ICM) to improve device behavior when cellular performance is inconsistent, achieving better availability, failover, and reconnection times.
ICM enables the system to respond to real-world variability in connectivity without manual intervention, helping maintain access availability during critical delivery windows.
Here’s what the ICM does in more detail:
Monitoring: ICM continuously monitors device performance using:
EventBridge to capture real-time events
Redshift for historical trend analysis
Step Functions to coordinate health checks and remediation workflows
S3 for storage and processing support
Analysis: The system identifies poorly performing devices by evaluating recent interaction history and applying defined rules.
Remediation: When issues are detected, ICM triggers automated corrective actions such as:
Rebooting the device
Rescanning the network
Switching cellular carriers
If these measures are not sufficient, the metrics help the operations team determine when manual servicing is required.
Phase 3: Platform Expansion
As Amazon Key matured, the team shifted its focus from solving Amazon's internal delivery challenges to building a general-purpose access platform. The system had already proven it could scale reliably. The next step was to extend that capability to external delivery providers.
In 2023, Amazon Key announced its integration with Grubhub. This marked the transition from a closed product to a more extensible platform. To support this, the team introduced a new architectural component: the Partner Gateway Service.
This service acts as a boundary between Amazon Key's internal systems and third-party applications. It exposes a clean, stable API that allows vetted external partners to request access to secure properties without revealing internal implementation details.
See the diagram below that shows the expanded architecture:
The Partner Gateway Service was designed to ensure that expansion did not compromise system integrity or performance. It provides features such as:
Partner onboarding workflows: Validates and registers new third-party delivery partners into the system.
Authentication and authorization: Ensures that only approved entities can request unlocks, and only under permitted conditions.
Rate limiting and security enforcement: Prevents abuse and isolates faults to protect core services.
Interface abstraction: Maintains a clear separation between partner-facing APIs and internal services to avoid tight coupling.
Security and Access Control
Amazon Key uses different authentication and authorization mechanisms for internal and third-party delivery systems, tailored to their integration models and security requirements.
For Amazon’s internal delivery flow, authentication is performed by AMZL (Amazon Logistics) services when a driver uses the Flex App. Once the delivery associate arrives at the property and it has been verified that the specific driver has an assigned delivery for that property at this time, Amazon Key’s backend issues a short-lived token to unlock the gate. This token is used to authorize access during the delivery attempt.
For third-party delivery providers, mutual TLS (mTLS) is used for authentication during the onboarding process. A profile is created per partner, and all communication is secured through mTLS to validate both client and server identities. The Partner Gateway Service handles authorization and request orchestration for these external systems.
Some key points shared by Vijay Nagarajan regarding access expiry and revocation are as follows:
Access is controlled through a time-bound token issued when the driver arrives and parks at the location.
The token is extended at 30-second intervals during the delivery window to maintain access while the delivery is in progress.
In failure scenarios, such as device unavailability due to power loss, the system notifies the driver through the Flex App that 1-click access is not available. In such cases, the drivers can continue accessing the property through standard access mechanisms (for example, through the lobby). One such example cited was power loss during a hurricane in Florida, which made certain devices unreachable.
Architectural Boundaries and Team Ownership
Operating so many services and features requires Amazon Key to ensure a clean separation of concerns. Here’s a quick look at the distribution of responsibility and the overall team composition.
The Gateway Service is responsible for performing authentication and authorization, and for orchestrating requests from client applications.
The Access Management Service stores and manages the relationships between devices, access points, installation jobs, and address mappings.
The Partner Gateway Service also handles authentication and authorization, using mutual TLS (mTLS), and orchestrates requests from external delivery partners.
The Device Service does not hold contextual information about where a device is located. Instead, it maintains knowledge about the type of device and the operations it supports.
The backend infrastructure team is responsible for managing all these services. The broader team is organized into three focus areas:
App Development
Front-End Development
Backend Common Infrastructure
Results and Impact
By rethinking both hardware and software architecture, Amazon Key was able to evolve from a niche internal solution focused on delivery associates into a large-scale, extensible access control platform. The results reflect a system that is not only convenient, secure, reliable and adaptable to operational realities, but also now serves a wide variety of audiences including: property owners/managers, residents, and guests, across single-family, multifamily, and commercial properties.
Today, Amazon Key supports over 100 million successful unlocks annually with extremely high system availability and low end-to-end latency from app tap to physical unlock. Because of this, first-attempt delivery success has improved, and defects per building has reduced.
These improvements directly contributed to more efficient deliveries, lower support costs, and a more seamless access control experience, at scale.
Learnings
Here are some key learnings from Amazon Key’s experience building their system:
Evolve as You Scale: The initial serverless design was ideal for fast iteration, but couldn’t support the demands of a global system with strict latency and connectivity requirements. Transitioning to ECS Fargate enabled more consistent performance and stateful processing.
Measure What Matters: Instead of measuring generic uptime, the team focused on availability during delivery hours. This shifted the optimization focus to periods that affect end users, resulting in more actionable metrics and better system tuning.
Standardization Enables Speed: Using a consistent tech stack (Java across services, Infrastructure as Code, and AWS-native tooling) allowed the team to move faster without sacrificing maintainability. Reuse became a strength rather than a constraint.
Plan for Imperfect Environments: Many design decisions assume ideal conditions. In practice, field deployments introduced a range of variables: poor signal strength, hardware variation, and environmental impact. Designing with these constraints in mind was key to building resilience.
Operate Based on Data: By feeding all system metrics into a centralized analytics pipeline, the team could proactively identify issues, validate changes, and understand usage patterns. This led to faster incident response and continuous system improvement.
Use Tools Where They Fit: Lambda was not abandoned entirely. It remained useful for stateless, low-latency tasks. However, core workflows were moved to ECS for predictability and control. Tool choice became a matter of fit, not philosophy.
Design for Growth: The Partner Gateway Service shows the value of designing for extensibility. It enabled Amazon Key to expand from a single-use product into a multi-tenant platform, supporting external partners without disrupting core operations.
At the end, Vijay Nagarajan shared one key point regarding the journey: “It’s easy to say we would have arrived at the scaling architecture right away. But there are so many unknowns when we scale, especially in the business we are in. We have to inevitably grow through the learning phase. We could have potentially accelerated the learning phase by getting some of the basic metrics/telemetry from the device and prioritizing the OTA infrastructure. But for the rest, we are evolving in the right direction.”
SPONSOR US
Get your product in front of more than 1,000,000 tech professionals.
Our newsletter puts your products and services directly in front of an audience that matters - hundreds of thousands of engineering leaders and senior engineers - who have influence over significant tech decisions and big purchases.
Space Fills Up Fast - Reserve Today
Ad spots typically sell out about 4 weeks in advance. To ensure your ad reaches this influential audience, reserve your space now by emailing sponsorship@bytebytego.com.
Like
Comment
Restack
© 2025 ByteByteGo
548 Market Street PMB 72296, San Francisco, CA 94104
Unsubscribe
by "ByteByteGo" <bytebytego@substack.com> - 11:36 - 28 May 2025 -
solar bracket
Hello Info，
We are professional manufacture for kinds of solar brackets since 2003, like strut, C profile, custom profile,Z profile, W profile....
All our products are manufactured in strict accordance with PPAP. We are high level supplier of SUNPOWER, which is one of the biggest solar tracker system and solar pannel company in the world since 2016.
Looking forward to hear from you soon!
Thank you and warm regards!
by "Bradford Keis" <keisbradford60@gmail.com> - 05:06 - 28 May 2025 -
The upskilling opportunity for workers
Only McKinsey Perspectives
Brought to you by Alex Panas, global leader of industries, & Axel Karlsson, global leader of functional practices and growth platforms
Welcome to the latest edition of Only McKinsey Perspectives. We hope you find our insights useful. Let us know what you think at Alex_Panas@McKinsey.com and Axel_Karlsson@McKinsey.com.
—Alex and Axel
•
Making the switch. As new technologies transform the way people work, upskilling that enables individuals to switch occupations will become even more important, McKinsey Senior Partners Kweilin Ellingrud and Nora Gardner and their coauthors state. Fortunately, US workers have a history of embracing occupational change. In fact, the latest McKinsey American Opportunity Survey (conducted in August 2024) finds that 17% of employed US respondents have switched to a different occupation since March 2020.
—Edited by Belinda Yu, editor, Atlanta
This email contains information about McKinsey's research, insights, services, or events. By opening our emails or clicking on links, you agree to our use of cookies and web tracking technology. For more information on how we use and protect your information, please review our privacy policy.
You received this email because you subscribed to the Only McKinsey Perspectives newsletter, formerly known as Only McKinsey.
Copyright © 2025 | McKinsey & Company, 3 World Trade Center, 175 Greenwich Street, New York, NY 10007
by "Only McKinsey Perspectives" <publishing@email.mckinsey.com> - 01:42 - 28 May 2025 -
Missed the event? Catch the insights today!
Couldn’t make it to SAP Sapphire?
Unlock exclusive access to on‑demand content today!
Check out all the excitement from SAP Sapphire at your convenience with our virtual on‑demand experience:
•
Get exclusive access to the top moments from this year’s event, including keynotes, exclusive interviews, product demos, solution-specific session highlights, and more.
•
Explore the SAP Sapphire Innovation Guide, a chapter-by-chapter look at the innovations announced at this year’s event, including the latest and greatest on the power of SAP Business Suite and how SAP Business AI is driving tangible business results.
•
Watch the recap video to get a glimpse into the sights and sounds of SAP Sapphire
Mark your calendar
Register today for an
upcoming local event:SAP NOW AI Tour
Coming to a city near youSAP Business Suite Innovation Days
Coming to a city near youSign up to get notified
when registration opens:SAP Connect
Oct 6–9 | Las Vegas & VirtualSAP TechEd
Nov 4–6 | Berlin & VirtualDiscover more
Discover the ways SAP can help you adopt the latest innovations to derive immediate and ongoing value from your solutions.
Rate your favorite SAP solutions by submitting your reviews. Published reviews receive a $25 USD gift card.
SAP Business Suite Webinar Series
Join us starting on June 24th to explore how Business Suite helps you adapt, scale, and lead in a changing world.
SAP (Legal Disclosure | SAP)
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.You are receiving this e-mail for one or more of the following reasons: you are an SAP customer, you were an SAP customer, SAP was asked to contact you by one of your colleagues, you expressed interest in one or more of our products or services, or you participated in or expressed interest to participate in a webinar, seminar, or event. SAP Privacy Statement
This e-mail was sent to you on behalf of the SAP Group with which you have a business relationship. If you would like to have more information about your Data Controller(s) please click here to contact webmaster@sap.com.
This promotional e-mail was sent to you by SAP Global Marketing and provides information on SAP's products and services that may be of interest to you. If you would prefer not to receive such e-mails from SAP in the future, please click on the Unsubscribe link.
To ensure you continue to receive SAP related information properly please add sap@mailsap.com to your address book or safe senders list.
by "SAP Sapphire" <sap@mailsap.com> - 09:20 - 27 May 2025 -
Quality Cable Ties & Seals for Your business
Dear Info
I am reaching out to introduce our company, a trusted supplier of consumer electronics. We specialize in Type-C, HDMI, and USB cables, providing top-tier connectivity solutions for various devices.
In addition to cables, we offer mobile phone cases, headphones, and DP and AV cables. Each product is crafted for superior quality, ensuring long-lasting use and user satisfaction.
We would love the opportunity to work with you and discuss how our products can fit your needs. Please feel free to reach out for further details.
Best regards,
Wenzhou Accory Security Seals CO., Ltd
by "Yaily Mortin" <mortinyaily@gmail.com> - 07:13 - 27 May 2025 -
How circularity can make the built environment more sustainable
Share this email
Brought to you by Aditya Sanghvi (Aditya_Sanghvi@McKinsey.com) and Daniele Chiarella (Daniele_Chiarella@McKinsey.com), global leaders of McKinsey’s Real Estate Practice
This email contains information about McKinsey’s research, insights, services, or events. By opening our emails or clicking on links, you agree to our use of cookies and web tracking technology. For more information on how we use and protect your information, please review our privacy policy.
You received this email because you subscribed to our McKinsey Quarterly alert list.
Copyright © 2025 | McKinsey & Company, 3 World Trade Center, 175 Greenwich Street, New York, NY 10007
by "McKinsey Quarterly" <publishing@email.mckinsey.com> - 02:20 - 27 May 2025 -
Discover your perfect writing tool - High-quality pen
Dear Info,
Are you looking for high-quality writing tools to enhance your writing experience? Our company was founded in 2014 by an elite team with more than 20 years of experience in the pen industry. Over the years, we have been committed to providing customers with high-quality writing tools and have cooperated with many well-known pen brands at home and abroad for OEM and ODM.
Now, we recommend the following high-quality products for you:
1. Signature pen
2. Ballpoint pen
3. Metal pen
4. Fountain pen
5. Gift pen setChoosing our products means you can trust their high quality and excellent performance. Act now to discover more surprises and enhance your writing experience!
For more details, please visit our website or contact our customer service team.
Sincerely,
Susan Wang
Shanghai Wenzhuo Industrial Co., Ltd,
website :https://cnwinjoy.m.en.alibaba.com
by "wenzhuopencil" <wenzhuopencil@shwenzhuo.com> - 01:43 - 27 May 2025 -
Remote EOR now supports more of the employment journey
Remote EOR now supports more of the employment journey
Hi MD,
Hiring globally is easy. Managing employment across multiple countries, systems, and teams? That’s where most EORs show their limits.
Remote is built for growing companies that want to reduce complexity, mitigate risk, and scale with confidence: smarter workflows, built-in compliance, and all in one place.
👀 EOR is changing fast; here’s how top teams are using it today.
Join us on June 17 for a live session with leaders from Remote’s product and ops teams, plus HR leadership from Semrush, a global SaaS company scaling their workforce with Remote across multiple markets.
We’ll share how companies are using Remote not just to hire, but to manage employment end-to-end, anywhere in the world.What’s new:
✅ Ask an Expert
1:1 video calls with in-house HR, legal, and tax professionals
✅ Compliance Watchtower
Track legal changes of legal changes across the world, surfaced directly in-platform
✅ Background checks
Run compliant pre-employment screening globally
✅ Equity Essentials
Support global equity with local tax guidance and employee visibility
✅ Device management
Provision and track hardware for international employees, fully managed
📞 Ready to explore Remote EOR for your team? Talk to sales
You received this email because you are subscribed to
News & Offers from Remote Europe Holding B.V
Update your email preferences to choose the types of emails you receive.
Unsubscribe from all future emailsRemote Europe Holding B.V
Copyright © 2025 Remote Europe Holding B.V All rights reserved.
Kraijenhoffstraat 137A 1018RG Amsterdam The Netherlands
by "Remote Team" <hello@remote-comms.com> - 01:30 - 27 May 2025 -
How Uber Eats Handles Billions of Daily Search Queries
How Uber Eats Handles Billions of Daily Search Queries
Forwarded this email? Subscribe here for moreBe part of P99 CONF – All things performance (Sponsored)
Obsessed with performance and low latency engineering? Discuss your optimizations and lessons learned with ~30K like-minded engineers… at P99 CONF 2025!
P99 CONF is a highly technical conference known for lively discussion. ScyllaDB makes it free and virtual, so it’s open to experts around the world. Core topics for this year include Rust, Zig, databases, event streaming architectures, measurement, compute/infrastructure, Linux, Kubernetes, and AI/ML.
If you’re selected to speak, you’ll be in amazing company. Past speakers include the creators of Postgres, Bun, Honeycomb, tokio, and Flask – plus engineers from today’s most impressive tech leaders.
Bonus: Early bird registrants get 30-day access to the complete O’Reilly library & learning platform, plus free digital books
SUBMIT YOUR TALK - OR ACCESS A FREE PASS
Disclaimer: The details in this post have been derived from the articles/videos shared online by the Uber Eats engineering team. All credit for the technical details goes to the Uber Eats Engineering Team. The links to the original articles and videos are present in the references section at the end of the post. We’ve attempted to analyze the details and provide our input about them. If you find any inaccuracies or omissions, please leave a comment, and we will do our best to fix them.
Uber Eats set out to increase the number of merchants available to users by a significant multiple. The team referred to it as nX growth. This wasn’t a simple matter of onboarding more restaurants. It meant expanding into new business lines like groceries, retail, and package delivery, each with its scale and technical demands.
To accommodate this, the search functionality needed to support this growth across all discovery surfaces:
Home feed, where users browse curated carousels.
Search, covering restaurant names, cuisines, and individual dishes.
Suggestions, which include autocomplete and lookahead logic.
Ads, which plug into the same backend and share the same constraints.
The challenge wasn’t just to show more. It was to do so without increasing latency, without compromising ranking quality, and without introducing inconsistency across surfaces.
A few core problems made this difficult:
Vertical expansion: Grocery stores often include over 100,000 items per location. Retail and package delivery add their indexing complexity.
Geographic expansion: The platform shifted from neighborhood-level search to intercity delivery zones.
Search scale: More merchants and more items meant exponential growth in the number of documents to index and retrieve.
Latency pressure: Every additional document increases compute costs in ranking and retrieval. Early attempts to scale selection caused 4x spikes in query latency.
To support nX merchant growth, the team had to rethink multiple layers of the search stack from ingestion and indexing to sharding, ranking, and query execution. In this article, we look at the breakdown of how Uber Eats rebuilt its search platform to handle this scale without degrading performance or relevance.
The 2025 State of Testing in DevOps Report (Sponsored)
mabl’s 6th State of Testing in DevOps Report explores the impact of software testing, test automation, organizational growth, and DevOps maturity across the software development lifecycle.
Search Architecture Overview
Uber Eats search is structured as a multi-stage pipeline, built to balance large-scale retrieval with precise, context-aware ranking.
Each stage in the architecture has a specific focus, starting from document ingestion to final ranking. Scaling the system for millions of merchants and items means optimizing each layer without introducing bottlenecks downstream.
Ingestion and Indexing
The system ingests documents from multiple verticals (restaurants, groceries, retail) and turns them into searchable entities.
There are two primary ingestion paths:
Batch Ingestion: Large-scale updates run through Apache Spark jobs. These jobs transform raw source-of-truth data into Lucene-compatible search documents, partition them into shards, and store the resulting indexes in an object store. This is the backbone for most index builds.
Streaming Ingestion: Real-time updates flow through Kafka as a write-ahead log. A dedicated ingestion service consumes these updates, maps them to the appropriate shard, and writes them into the live index.
Priority-Aware Ingestion: Not all updates are equal. The system supports priority queues so urgent updates, like price changes or store availability, are ingested ahead of less critical ones. This ensures high-priority content reflects quickly in search results.
Retrieval Layer
The retrieval layer acts as the front line of the search experience. Its job is to fetch a broad set of relevant candidates for downstream rankers to evaluate.
Recall-focused retrieval: The system fetches as many potentially relevant documents as possible, maximizing coverage. This includes stores, items, and metadata mapped to the user’s location.
Geo-aware matching: Given that most searches are tied to physical delivery, the retrieval process incorporates location constraints using geo-sharding and hex-based delivery zones. Queries are scoped to shards that map to the user’s region.
First-Pass Ranking
Once the initial candidate set is retrieved, a lightweight ranking phase begins.
Lexical matching: Uses direct term overlap between the user’s query and the indexed document fields.
Fast filtering: Filters out low-relevance or out-of-scope results quickly, keeping only candidates worth further evaluation.
Efficiency-focused: This stage runs directly on the data nodes to avoid unnecessary network fanout. It's designed for speed, not deep personalization.
Hydration Layer
Before documents reach the second-pass ranker, they go through a hydration phase.
Each document is populated with additional context: delivery ETAs, promotional offers, loyalty membership info, and store images. This ensures downstream components have all the information needed for ranking and display.
Second-Pass Ranking
This is where the heavier computation happens, evaluating business signals and user behavior.
Personalized scoring: Models incorporate past orders, browsing patterns, time of day, and historical conversion rates to prioritize results that match the user’s intent.
Business metric optimization: Ranking is also shaped by conversion likelihood, engagement metrics, and performance of past campaigns, ensuring search results aren’t just relevant, but also effective for both user and platform.
The Query Scaling Challenge
Scaling search isn't just about fetching more documents. It's about knowing how far to push the system before performance breaks.
At Uber Eats, the first attempt to increase selection by doubling the number of matched candidates from 200 to 400 seemed like a low-risk change. In practice, it triggered a 4X spike in P50 query latency and exposed deeper architectural flaws.
The idea was straightforward: expand the candidate pool so that downstream rankers have more choices. More stores mean better recall. However, the cost wasn’t linear because of the following reasons:
Search radius grows quadratically: Extending delivery range from 5 km to 10 km doesn’t double the document count—it increases the search area by a factor of four. Every added kilometer pulls in a disproportionately larger set of stores.
Retrieval becomes I/O-bound: The number of documents per request ballooned. Queries that once matched a few thousand entries now had to sift through tens of thousands. The Lucene index, tuned for fast lookups, started choking during iteration.
Geo-sharding Mismatches
The geo-sharding strategy, built around delivery zones using hexagons, wasn't prepared for expanded retrieval scopes.
As delivery radii increased, queries began touching more distant shards, many of which were optimized for different traffic patterns or data distributions. This led to inconsistent latencies and underutilized shards in low-traffic areas.
Pipeline Coordination Gaps
Ingestion and query layers weren’t fully aligned.
The ingestion service categorizes stores as “nearby” or “far” based on upstream heuristics. These classifications didn’t carry over cleanly into the retrieval logic. As a result, rankers treated distant and local stores the same, skewing relevance scoring and increasing CPU time.
Geospatial Indexing with H3 and the Sharding Problem
Uber Eats search is inherently geospatial. Every query is grounded in a delivery address, and every result must answer a core question: Can this store deliver to this user quickly and reliably?
To handle this, the system uses H3, Uber’s open-source hexagonal spatial index, to model the delivery world.
H3-Based Delivery Mapping
Each merchant’s delivery area is mapped using H3 hexagons:
The world is divided into hexagonal tiles at a chosen resolution.
A store declares delivery availability to a specific set of hexes.
The index then builds a reverse mapping: for any hex, which stores deliver to it?
This structure makes location-based lookups efficient. Given a user’s location, the system finds their H3 hexagon and retrieves all matching stores with minimal fanout.
Source: Uber Engineering Presentation Where Ingestion Fell Short
The problem wasn’t the mapping but the metadata.
Upstream services were responsible for labeling stores as “close” or “far” at ingestion time. This binary categorization was passed downstream without actual delivery time (ETA) information.
Once ingested, the ranking layer saw both close and far stores as equivalent. That broke relevance scoring in subtle but important ways.
Consider this:
Hexagon 7 might have two stores marked as “far.”
One is 5 minutes away, the other 30.
To the search system, they look the same.
That lack of granularity meant distant but high-converting stores would often outrank nearby ones. Users saw popular chains from across the city instead of the closer, faster options they expected.
Sharding Techniques
Sharding determines how the system splits the global index across machines.
A good sharding strategy keeps queries fast, data well-balanced, and hotspots under control. A bad one leads to overloaded nodes, inconsistent performance, and painful debugging sessions.
Uber Eats search uses two primary sharding strategies: Latitude sharding and Hex sharding. Each has trade-offs depending on geography, query patterns, and document distribution.
Latitude Sharding
Latitude sharding divides the world into horizontal bands. Each band corresponds to a range of latitudes, and each range maps to a shard. The idea is simple: group nearby regions based on their vertical position on the globe.
Shard assignment is computed offline using Spark. The process involves two steps:
Slice the map into thousands of narrow latitude stripes.
Group adjacent stripes into N roughly equal-sized shards, based on document count.
To avoid boundary misses, buffer zones are added. Any store that falls near the edge of a shard is indexed in both neighboring shards. The buffer width is based on the maximum expected search radius, converted from kilometers into degrees of latitude.
The benefits of this approach are as follows:
Time zone diversification: Shards include cities from different time zones (for example, the US and Europe). This naturally spreads out traffic peaks, since users in different zones don’t search at the same time.
Query locality: Many queries resolve within a single shard. That keeps fanout low and speeds up ranking.
The downsides are as follows:
Shard imbalance: Dense urban areas near the equator (for example, Southeast Asia) pack far more stores per degree of latitude than sparsely populated regions. Some shards grow much larger than others.
Slower index builds: Indexing time is gated by the largest shard. Skewed shard sizes lead to uneven performance and increased latency.
Hex Sharding
To address the limitations of latitude sharding, Uber Eats also uses Hex sharding, built directly on top of the H3 spatial index. Here’s how it works:
The world is tiled using H3 hexagons at a fixed resolution (typically level 2 or 3).
Each hex contains a portion of the indexed documents.
A bin-packing algorithm groups hexes into N shards with roughly equal document counts.
Buffer zones are handled similarly, but instead of latitude bands, buffer regions are defined as neighboring hexagons at a lower resolution. Any store near a hex boundary is indexed into multiple shards to avoid cutting off valid results.
The benefits are as follows:
Balanced shards: Bin-packing by document count leads to far more consistent shard sizes, regardless of geography.
Better cache locality: Queries scoped to hexes tend to access tightly grouped data. That improves memory access patterns and reduces retrieval cost.
Less indexing skew: Because hexes are spatially uniform, indexing overhead stays predictable across regions.
As a takeaway, latitude sharding works well when shard traffic needs to be spread across time zones, but it breaks down in high-density regions.
Hex sharding offers more control, better balance, and aligns naturally with the geospatial nature of delivery. Uber Eats uses both, but hex sharding has become the more scalable default, especially as selection grows and delivery radii expand.
Index Layout Optimizations
When search systems slow down, it’s tempting to look at algorithms, infrastructure, or sharding. But often, the bottleneck hides in a quieter place: how the documents are laid out in the index itself.
At Uber Eats scale, index layout plays a critical role in both latency and system efficiency. The team optimized layouts differently for restaurant (Eats) and grocery verticals based on query patterns, item density, and retrieval behavior.
Eats Index Layout
Restaurant queries typically involve users looking for either a known brand or food type within a city. For example, “McDonald’s,” “pizza,” or “Thai near me.” The document layout reflects that intent.
Documents are sorted as:
City
Restaurant
Items within each restaurant
This works for the following reasons:
Faster city filtering: Queries scoped to San Francisco don’t need to scan through documents for Tokyo or Boston. The search pointer skips irrelevant sections entirely.
Improved compression: Lucene uses delta encoding. Grouping items from the same store, where metadata like delivery fee or promo is often repeated, yields tighter compression.
Early termination: Documents are sorted by static rank (for example, popularity or rating). Once the system retrieves enough high-scoring results, it stops scanning further.
Grocery Index Layout
Grocery stores behave differently. A single store may list hundreds or thousands of items, and queries often target a specific product ( “chicken,” “milk,” “pasta”) rather than a store.
Here, the layout is:
City
Store (sorted by offline conversion rate)
Items grouped tightly under each store
This matters for the following reasons:
Per-store budget enforcement: To avoid flooding results from one SKU-heavy store, the system imposes a per-store document budget. Once a store’s quota is met, the index skips to the next.
Diverse results: Instead of returning 100 versions of “chicken” from the same retailer, the layout ensures results are spread across stores.
Faster skip iteration: The tight grouping allows the system to jump across store boundaries efficiently, without scanning unnecessary items.
Performance Impact
The improvements of these indexing strategies were pretty good:
Retrieval latency dropped by 60%
P95 latency improved by 50%
Index size reduced by 20%, thanks to better compression
ETA-Aware Range Indexing
Delivery time matters. When users search on Uber Eats, they expect nearby options to show up first, not restaurants 30 minutes away that happen to rank higher for other reasons. But for a long time, the ranking layer couldn’t make that distinction. It knew which stores delivered to a given area but not how long delivery would take.
This is because the ingestion pipeline didn’t include ETA (Estimated Time of Delivery) information between stores and hexagons. That meant:
The system treated all deliverable stores as equal, whether they were 5 minutes or 40 minutes away.
Ranking logic had no signal to penalize faraway stores when closer alternatives existed.
Popular but distant stores would often dominate results, even if faster options were available.
This undermined both user expectations and conversion rates. A store that looks promising but takes too long to deliver creates a broken experience.
The Solution: Range-Based ETA Bucketing
To fix this, Uber Eats introduced ETA-aware range indexing. Instead of treating delivery zones as flat lists, the system:
Binned stores into time-based ranges: Each store was indexed into one or more delivery buckets based on how long it takes to reach a given hex. For example:
Range 1: 0 to 10 minutes
Range 2: 10 to 20 minutes
Range 3: 20 to 30 minutes
Duplicated entries across ranges: A store that’s 12 minutes from one hex and 28 minutes from another would appear in both Range 2 and Range 3. This added some storage overhead, but improved retrieval precision.
Ran range-specific queries in parallel: When a user queried from a given location, the system launched multiple subqueries—one for each ETA bucket. Each subquery targeted its corresponding shard slice.
This approach works for the following reasons:
Recall improves: The system surfaces more candidates overall, across a wider range of delivery times without overloading a single query path.
Latency drops: By splitting the query into parallel, bounded range scans, each shard does less work, and total response time shrinks.
Relevance becomes proximity-aware: Rankers now see not just what a store offers, but how fast it can deliver, enabling better tradeoffs between popularity and speed.
Conclusion
Scaling Uber Eats search to support nX merchant growth wasn’t a single optimization. It was a system-wide redesign.
Latency issues, ranking mismatches, and capacity bottlenecks surfaced not because one layer failed, but because assumptions across indexing, sharding, and retrieval stopped holding under pressure.
This effort highlighted a few enduring lessons that apply to any high-scale search or recommendation system:
Documents must be organized around how queries behave. Misaligned layouts waste I/O, increase iteration cost, and cripple early termination logic.
A good sharding strategy accounts for document distribution, query density, and even time zone behavior to spread traffic and avoid synchronized load spikes.
When profiling shows document iteration taking milliseconds instead of microseconds, the problem isn’t ranking but traversal. Optimizing storage access patterns often yields bigger wins than tuning ranking models.
Storing the same store in multiple ETA buckets increases index size, but dramatically reduces compute at query time. Every gain in recall, speed, or freshness has to be weighed against storage, complexity, and ingestion cost.
Breaking queries into ETA-based subranges, separating fuzzy matches from exact ones, or running proximity buckets in parallel all help maintain latency while expanding recall.
In a system touched by dozens of teams and services, observability is a prerequisite. Latency regressions, ingestion mismatches, and ranking anomalies can't be fixed without precise telemetry and traceability.
References:
SPONSOR US
Get your product in front of more than 1,000,000 tech professionals.
Our newsletter puts your products and services directly in front of an audience that matters - hundreds of thousands of engineering leaders and senior engineers - who have influence over significant tech decisions and big purchases.
Space Fills Up Fast - Reserve Today
Ad spots typically sell out about 4 weeks in advance. To ensure your ad reaches this influential audience, reserve your space now by emailing sponsorship@bytebytego.com.
© 2025 ByteByteGo
548 Market Street PMB 72296, San Francisco, CA 94104
Unsubscribe
by "ByteByteGo" <bytebytego@substack.com> - 11:36 - 27 May 2025 -
Missed Out? Join the Waiting List
Hi Sir/Madam,
Unfortunately, our final partnership slot at Poulton Park Golf Club has been taken.
However, due to incredible demand, we’re creating a waiting list for future opportunities at this prestigious venue. Let me know if you’d like to be added, and I’ll keep you updated on upcoming openings.
If you’re still interested in elevating your brand in the local area, I’d be happy to explore alternative options for Your Telecoms Consultant.
Looking forward to hearing from you.Best regards,
James Thomson
Account Manager
+44 (0)7453 145 120
by "James Thomson - Golf Marketing Agency" <info@golfmarketingagency.co.uk> - 08:30 - 27 May 2025 -
High-performance semiconductor components help you lead the market
Dear Sir/Madam,
Hope you are well when you receive this message.
My name is David, I am from Shenzhen Zhanrui Electronics Co., Ltd. Our company's business covers component procurement, PCBA turnkey services and PCBA processing, functional testing, product assembly, etc.
We are committed to improving the supply chain value-added service provider for users in the semiconductor industry, and have been providing advanced services to customers and the market with high quality, high efficiency and high standards. The brands we distribute include TI, ON, ADI, ST, NXP, ALTERA, XILINX, INFINEON, BROADCOM, MICROCHIP, INTERSIL, FAIRCHILD, TOSHIBA, Vicor, etc.
Here are some of the main advantages we provide:
1. Company advantages: professional component agent distributor, providing high-quality components, complete solutions and technical support services.
2. Competitive price: dedicated to reducing the comprehensive cost of customers to ensure that your project is cost-effective.
3. Quick response: Our efficient supply chain management ensures fast order delivery.
4. Innovative service solutions: We continue to leverage our strengths to provide our customers with better products, more comprehensive services, and improved technology.
We look forward to establishing a long-term partnership with your company to improve the market competitiveness of your company's products.
Sincerely,
David Ouyang
Shenzhen Zhanrui Electronics Co., Ltd.
by "Cypa Hnatyk" <cypahnatyk@gmail.com> - 08:18 - 27 May 2025 -
You're Invited! Product Expert Series: Intelligent Observability for Security Management
New Relic
Are you spending too much time tackling irrelevant vulnerabilities while critical threats linger?
Join us for Product Expert Series, Episode 4 on 28 May at 10 AM BST and learn how to make security smarter and faster. Our experts will demo groundbreaking tools that automatically prioritise runtime vulnerabilities posing actual risks and share best practices for saving DevOps teams invaluable time.
The live demo and Q&A session will focus on how to:
- Minimise interruptions with prioritised and actionable security findings from Security RX.
- Gain precision insights from existing APM and infra agents, eliminating time wasted on vulnerabilities that don’t matter.
- Answer your specific questions and unique use cases.
This session will empower you to streamline your security actions and elevate your team’s efficiency.
Save your spot today and take a smarter approach to enhance your security posture.
Register Now
by "New Relic" <emeamarketing@newrelic.com> - 05:01 - 27 May 2025 -
How can the world’s healthcare worker shortage be solved?
On McKinsey Perspectives
Brought to you by Alex Panas, global leader of industries, & Axel Karlsson, global leader of functional practices and growth platforms
Welcome to the latest edition of Only McKinsey Perspectives. We hope you find our insights useful. Let us know what you think at Alex_Panas@McKinsey.com and Axel_Karlsson@McKinsey.com.
—Alex and Axel
•
Advancing health. Over the past century, people have lived longer, but the amount of time they spend in poor health hasn’t changed. Looking forward, the potential shortage of healthcare workers means that those who require care won’t always have access to the services they need, according to McKinsey Senior Partner Pooja Kumar and coauthors. Addressing the healthcare worker shortage is a profound opportunity to advance global health. According to a McKinsey Health Institute (MHI) analysis, closing this gap could avert 189 million years of life lost to early death and lived with a disability.
—Edited by Belinda Yu, editor, Atlanta
This email contains information about McKinsey's research, insights, services, or events. By opening our emails or clicking on links, you agree to our use of cookies and web tracking technology. For more information on how we use and protect your information, please review our privacy policy.
You received this email because you subscribed to the Only McKinsey Perspectives newsletter, formerly known as Only McKinsey.
Copyright © 2025 | McKinsey & Company, 3 World Trade Center, 175 Greenwich Street, New York, NY 10007
by "Only McKinsey Perspectives" <publishing@email.mckinsey.com> - 11:05 - 26 May 2025 -
Get Ahead: Insights, Innovations, and AI Strategies to Power Growth
Agentforce:
Empowering Growth with AITransforming ASEAN Business with AI
Agentforce Virtual Event
Agentforce World Tour Broadcast
Join us to elevate your business with Agentforce! Discover innovative ways to enhance relationships, boost productivity, and customer engagement. Be inspired by keynotes, demos, and success stories from Trailblazers. Unlock the benefits of Agentforce, deeply integrated with Salesforce. We can’t wait to welcome you!
Register now 
Live webinar
Overcome Scheduling Complexity: Optimise Your Field Service with Agentforce
Struggling to schedule the right field resource at the right time? Even a few appointments can create millions of combinations. Join our live webinar on 8 July 2025 to see how Salesforce Field Service and Agentforce use AI to simplify scheduling, boost productivity, and enhance customer satisfaction. Includes a live demo and Q&A.
Watch now 
ASEAN Trailblazer Spotlight
United Tractors increases uptime for customers with Field Service
United Tractors boosts uptime and customer satisfaction by digitising its field service with Salesforce. Discover how the team improved SLA compliance from 75% to 97%, connected sales and service data, and built new digital capabilities to better serve customers across Indonesia.
Find out more 
ESMB
The Guide to AI for Small Businesses
Small businesses are embracing AI to boost efficiency and growth. Our guide explores how lean teams can use AI to focus on what matters most: serving customers and scaling smart. Get practical tips, use cases, and tools to unlock real productivity gains.
Get the guide 
Commerce
Third Edition: State of Commerce
Discover the latest trends in commerce from 2,700 leaders and 1.5 billion customers. The State of Commerce report reveals how AI is driving investment, the key challenges businesses face, and the growing importance of customer trust and scalability in shaping the future of commerce.
Read the report What's On
Unlocking Growth: AI and Tech Strategies for SMB Success in 2025
Industry - Financial Services
Agentforce for Financial Services
Ready to transform your customer experience? Watch the Agentforce demo to see how leading financial firms are using AI and automation to boost revenue and build trusted relationships - faster than ever.
The Power of Two: Insights made easy with Salesforce + Tableau
On Demand Webinar
Unlock the Power of Unstructured Data for Agentic AI: New Insights from CIOs
Unstructured data is transforming the future of AI. Watch our on-demand webinar to discover how leading CIOs are using it to power autonomous agents, unlock innovation, and deliver smarter, more personalised customer experiences across industries.
© 2025 Salesforce, Inc.
Salesforce.com Singapore Pte Ltd. 5 Temasek Boulevard #13-01 Suntec Tower 5 Singapore 038985
General Inquiries: +65 6302 5700
This email was sent to info@learn.odoo.com
Manage Preferences to Unsubscribe | View as webpage | Privacy Statement
Powered by Salesforce Marketing Cloud
by "Salesforce" <salesforce@mail.salesforce.com> - 11:02 - 26 May 2025 -
Wholesale Solar Poles for Middle East Distributors – 35% Margin & OEM Branding
Dear Info,
[Jiangsu Shangying Photoelectric Technology Co.,Ltd] is a trusted manufacturer of solar poles and power poles for the Middle East market. We offer high-margin opportunities with private labeling, bulk pricing, and reliable logistics** to grow your business.
Why Work with Us?
1.Profit-Driven Pricing:
- 35%+ distributor margins (poles from $55/unit for 500+ MOQ).
- Exclusive territory discounts for key partners.
2.Customization & Branding:
- OEM/ODM services: Add your logo, packaging, and certifications.
- Adapt designs to local standards (UAE.S 5019-2018).
3.Supply Chain Reliability:
- DDP shipping to major ports (Jebel Ali/Dammam).
- 99% on-time delivery rate in 2024.
Attached: Wholesale catalog and distributor agreement template.
Start Today: Claim your free sample by replying to this email or WhatsApp +86 17705276414
Best regards,
[Daniel]
[Sales Maneger]
[Jiangsu Shangying Photoelectric Technology Co.,Ltd ]
by "sales16" <sales16@jssunteklights.com> - 07:54 - 26 May 2025
