How Mapbox Scales over 9 AWS Regions

•

0 likes•726 views

Johan

Slides from Devops Madrid in November 2015 http://www.meetup.com/madrid-devops/events/225555911/

Technology

How Mapbox Scales
Over 9 Data Centers
Johan
@freenerd
johan@mapbox.com
Madrid DevOps November 2015
1

• What is Mapbox?
• 9 data centers?
• Tracing a map request
2

• What is Mapbox?
• 9 Data Centers?
• Tracing a map request
7

9 Data Centers?
• Why run this in many regions?
• One region = cheaper, less complex, easier to build and
maintain
11

9 Data Centers?
• Global high availability
• Global low latency
12

9 Data Centers?
Global high availability
13

9 Data Centers?
Global high availability
• Mapbox is critical infrastructure for our customers
• Mapbox SLA: 99.9%
• Problems for high availability
• AWS problems
• Mapbox software or conﬁguration problems
• Critical deploys
14

9 Data Centers?
• Global high availability
• Global low latency
15

9 Data Centers?
Global low latency
• Can't beat the speed of light
• Latency is critical for using a map
• Bring our data closer to our users
17

9 Data Centers?
• Global high availability
• Global low latency
18

• Grid over the world
• Every cell of the grid is a tile
• Different zoomlevels
• Zoomlevel 0 is the world
• Zoomlevel 13 is a city
• Every tile is identiﬁed by mapid,
coordinates and zoomlevel
24

Client
• Browser loads Javascript
• Mapbox.js allows for customizing map with very few lines
• Javascript
• Determine viewport
• Request each individual tile
26

Client
https://tiles.mapbox.com/v4/
map.id/17/70428/42997.png?access_token=pk.xxx
27

CDN
• Content Distribution Network
• Physical cache close to users
• AWS: Cloudfront
• Others: Akamai, Fastly, CloudFlare
29

CDN
• When a request comes in:
• Find nearest edge location
• Terminate TLS
• Match request to behaviour
• Look in cache (based on URL & Query String)
• If object is there: return
31

CDN
• Your CDN works best if it can serve everything from cache
• How to remove stale data?
• Trade-off: high cache hit rate vs. update delay
• Time-To-Live when a cached object expires
• We use 5 minutes
• 35 % cache hit rate
32

DNS
• Originally: Resolve domain names to IP addresses
• Also: Route request to nearest data center
• best region for request based historic on latency
• Amazon: Route53
• Others: Dyn, easyDNS, Akamai
34

Load Balancer
• Route requests to application servers
• Entry point to a region
• AWS: Elastic Load Balancer (ELB)
• Others: haproxy, nginx, f5
37

Load Balancer
• Terminate TLS
• Determine which application server to route to
• Healthy server
• ELB: Server with least outstanding requests
• Wait for results and return
38

Application Servers
• Virtual Machines
• AWS: Elastic Compute Cloud (EC2)
• Others: Google Compute Cloud, Rackspace, Digital Ocean
40

Application Servers
• c3.xlarge instances
• Ubuntu Linux
• Node.js/Express
41

Application Servers
• Authenticate
• Load map data
• Fetch tile and return
42

DynamoDB
• Primary/Replica
• Reads to replicas, writes only to
primary
• Replicas only in 2 regions
• Reads for non-replica regions need
to go over the Internet
• In-instance caching of
authentication/map information
1
https://www.mapbox.com/blog/scaling-the-mapbox-infrastructure-with-
dynamodb-streams/
44

Application Servers
Fetch tiles
• check simultanously in cache (redis) and object store (s3)
• return from where is found ﬁrst
• if only found in object store, update local cache
46

Application Servers
• redis is used as least-recently used cache, thus popular tiles
for a region are usually cached
• s3 is slow, because data is in us-east-1 bucket only
• Stats:
• 80% cache hits
• r3.4xlarge with 122 GB of memory
47

Thanks
• What is Mapbox?
• 9 Data Centers?
• Tracing a Map Request
@freenerd
johan@mapbox.com
53

Elasticity
• EC2 instances are provisioned via Auto Scaling Group
• Auto Scaling is based on instance CPU load
• Scale up/down if CPU load over/under 55%/20% for 2
minutes
55

What's hot

Lambda Architecture has been a common way to build data pipelines for a long time, despite difficulties in maintaining two complex systems. An alternative, Kappa Architecture, was proposed in 2014, but many companies are still reluctant to switch to Kappa. And there is a reason for that: even though Kappa generally provides a simpler design and similar or lower latency, there are a lot of practical challenges in areas like exactly-once delivery, late-arriving data, historical backfill and reprocessing. In this talk, I want to show how you can solve those challenges by embracing Apache Kafka as a foundation of your data pipeline and leveraging modern stream-processing frameworks like Apache Kafka Streams and Apache Flink.

It's Time To Stop Using Lambda Architecture | Yaroslav Tkachenko, Shopify

HostedbyConfluent

Geode - Day 2

Swapnil Bawaskar

Presented at Stream Processing Meetup (7/19/2018)(https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/251481797/). At Uber, we operate 20+ Kafka clusters to collect system and application logs as well as event data from rider and driver apps. We need a Kafka replication solution to replicate data between Kafka clusters across multiple data centers for different purposes. This talk will introduce the history behind uReplicator and the high level architecture. As the original uReplicator ran into scalability challenges and operational overhead as the scale of Kafka clusters increased, we built the Federated uReplicator which addressed above issues and provide an extensible architecture for further scaling.

uReplicator: Uber Engineering’s Scalable, Robust Kafka Replicator

Michael Hongliang Xu

Scalable IoT platform

Swapnil Bawaskar

Kafka Summit SF 2017 - Fast Data in Supply Chain Planning

confluent

Building data pipelines is pretty hard! Building a multi-datacenter active-active real time data pipeline for multiple classes of data with different durability, latency and availability guarantees is much harder. Real time infrastructure powers critical pieces of Uber (think Surge) and in this talk we will discuss our architecture, technical challenges, learnings and how a blend of open source infrastructure (Apache Kafka and Samza) and in-house technologies have helped Uber scale.

Hadoop summit - Scaling Uber’s Real-Time Infra for Trillion Events per Day

Ankur Bansal

The Benefits of Publicly-Accessible Data - SNODAS

Thomas Horner

Kafka is a vital part of data infrastructure in many organizations. When the Kafka cluster grows and more data is stored in Kafka for a longer duration, several issues related to scalability, efficiency, and operations become important to address. Kafka cluster storage is typically scaled by adding more broker nodes to the cluster. But this also adds needless memory and CPUs to the cluster making overall storage cost less efficient compared to storing the older data in external storage. Tiered storage is introduced to extend Kafka's storage beyond the local storage available on the Kafka cluster by retaining the older data in cheaper stores, such as HDFS, S3, Azure or GCS with minimal impact on the internals of Kafka. We will talk about - How tiered storage addresses the above problems and also brings several other advantages. - High level architecture of tiered storage - Future work planned as part of tiered storage.

Kafka Tiered Storage | Satish Duggana and Sriharsha Chintalapani, Uber

HostedbyConfluent

Kafka Summit SF 2017 - Real-Time Document Rankings with Kafka Streams

confluent

Moving from Lambda and Kappa Architectures to Kappa+ at Uber Kappa+ is a new approach developed at Uber to overcome the limitations of the Lambda and Kappa architectures. Whether your realtime infrastructure processes data at Uber scale (well over a trillion messages daily) or only a fraction of that, chances are you will need to reprocess old data at some point. There can be many reasons for this. Perhaps a bug fix in the realtime code needs to be retroactively applied (aka backfill), or there is a need to train realtime machine learning models on last few months of data before bringing the models online. Kafka's data retention is limited in practice and generally insufficient for such needs. So data must be processed from archives. Aside from addressing such situations, enabling efficient stream processing on archived as well as realtime data also broadens the applicability of stream processing. This talk introduces the Kappa+ architecture which enables the reuse of streaming realtime logic (stateful and stateless) to efficiently process any amounts of historic data without requiring it to be in Kafka. We shall discuss the complexities involved in such kind of processing and the specific techniques employed in Kappa+ to tackle them.

Flink Forward San Francisco 2019: Moving from Lambda and Kappa Architectures ...

Flink Forward

Organizations have a need to protect Personally Identifiable Information (PII). As Event Streaming Architecture (ESA) becomes ubiquitous in the enterprise, the prevalence of PII within data streams will only increase. Data architects must be cognizant of how their data pipelines can allow for potential leaks. In highly distributed systems, zero-trust networking has become an industry best practice. We can do the same with Kafka by introducing message-level security. A DevSecOps Engineer with some Kafka experience can leverage Kafka Streams to protect PII by enforcing role-based access control using Open Policy Agent. Rather than implementing a REST API to handle message-level security, Kafka Streams can filter, or even transform outgoing messages in order to redact PII data while leveraging the native capabilities of Kafka. In our proposed presentation, we will provide a live demonstration that consists of two consumers subscribing to the same Kafka topic, but receiving different messages based on the rules specified in Open Policy Agent. At the conclusion of the presentation, we will provide attendees with a GitHub repository, so that they can enjoy a sandbox environment for hands-on experimentation with message-level security.

Securing the Message Bus with Kafka Streams | Paul Otto and Ryan Salcido, Raf...

HostedbyConfluent

Kafka Summit NYC 2017 - Data Processing at LinkedIn with Apache Kafka

confluent

Powering an API with GraphQL, Golang, and NoSQL

Nic Raboy

Developing and operating real-time applications with Oceanus The Tencent Data team (data.qq.com) is responsible to build a reliable and scalable infrastructure for various products at Tencent including Tencent Games, Tencent Video and WeChat. We have to process over 1.6 trillion events per day and the peak throughput reaches 210 million per second. Such a large scale exposes great challenges in the developing and operating of real-time applications. In this talk, we will give an introduction to Oceanus, a platform built at Tencent to facilitate the development of real-time applications. We will introduce typical user cases and how applications are developed, deployed and monitored with Oceanus. We will also introduce the management of Flink jobs in Oceanus, together with some experience gained in our operating practice. Finally, we will discuss some efforts we have done to enhance the reliability and efficiency, e.g. master failover and local keyed streams.

Flink Forward San Francisco 2019: Developing and operating real-time applicat...

Flink Forward

InfluxData builds a time series platform primarily deployed for DevOps and IoT monitoring. This talk presents several lessons learned while scaling the platform across a large number of deployments—from single server open source instances to highly available high-throughput clusters. This talk presents a number of failure conditions that informed subsequent design choices. Ryan Betts (Director of Engineering at InfluxData) will discuss designing backpressure in an AP system with tens of thousands of resource-limited writers; trade-offs between monolithic and service-oriented database implementations; and lessons learned implementing multiple query processing systems.

InfluxData Internals by Ryan Betts

InfluxData

Case Study: Stream Processing on AWS using Kappa Architecture

Joey Bolduc-Gilbert

When your Kafka clusters start growing so is the cost associated with them. As administrators we have to ensure that the service we support is operating in the most reliable way to satisfy the customers. However, for our business it is as important that we ensure the same service is also cost-efficient. There are two ways we can optimize the cost of service – tuning broker machines and tuning the data transfers. Minimizing data transfer is the largest return on investment since that is what accounts for the most spend. With the use of Kafka administrative tools and metrics we can find multiple ways to reduce the data transfers in the clusters. The presentation will cover various techniques administrators of Kafka service can employ to reduce the data transfers and to save the operational costs. Reducing cross-AZ traffic, optimizing batching with use of DumpLogSegment script, utilizing Kafka metrics to shut down unused data streams and more. With an objective of making our Kafka deployment as cost effective as possible, we have gained money saving tricks. And we would love to share them with the community.

Administrative techniques to reduce Kafka costs | Anna Kepler, Viasat

HostedbyConfluent

In DiDi Chuxing Company, which is China’s most popular ride-sharing company. we use HBase to serve when we have a bigdata problem. We run three clusters which serve different business needs. We backported the Region Grouping feature back to our internal HBase version so we could isolate the different use cases. We built the Didi HBase Service platform which is popular amongst engineers at our company. It includes a workflow and project management function as well as a user monitoring view. Internally we recommend users use Phoenix to simplify access.even more,we used row timestamp;multidimensional table schema to slove muti dimension query problems C++, Go, Python, and PHP clients get to HBase via thrift2 proxies and QueryServer. We run many important buisness applications out of our HBase cluster such as ETA/GPS/History Order/API metrics monitoring/ and Traffic in the Cloud. If you are interested in any aspects listed above, please come to our talk. We would like to share our experiences with you.

HBaseCon2017 Apache HBase at Didi

HBaseCon

Flink forward SF 2017: Elizabeth K. Joseph and Ravi Yadav - Flink meet DC/OS ...

Flink Forward

The increasing number of available data sources in today's application stacks created a demand to continuously capture and process data from various sources to quickly turn high volume streams of raw data into actionable insights. Apache Flink addresses many of the challenges faced in this domain as it's specifically tailored to distributed computations over streams. While Flink provides all the necessary capabilities to process streaming data, provisioning and maintaining a Flink cluster still requires considerable effort and expertise. We will discuss how cloud services can remove most of the burden of running the clusters underlying your Flink jobs and explain how to build a real-time processing pipeline on top of AWS by integrating Flink with Amazon Kinesis and Amazon EMR. We will furthermore illustrate how to leverage the reliable, scalable, and elastic nature of the AWS cloud to effectively create and operate your real-time processing pipeline with little operational overhead.

Flink Forward Berlin 2017: Steffen Hausmann - Build a Real-time Stream Proces...

Flink Forward

What's hot (20)

It's Time To Stop Using Lambda Architecture | Yaroslav Tkachenko, Shopify

Geode - Day 2

uReplicator: Uber Engineering’s Scalable, Robust Kafka Replicator

Scalable IoT platform

Kafka Summit SF 2017 - Fast Data in Supply Chain Planning

Hadoop summit - Scaling Uber’s Real-Time Infra for Trillion Events per Day

The Benefits of Publicly-Accessible Data - SNODAS

Kafka Tiered Storage | Satish Duggana and Sriharsha Chintalapani, Uber

Kafka Summit SF 2017 - Real-Time Document Rankings with Kafka Streams

Flink Forward San Francisco 2019: Moving from Lambda and Kappa Architectures ...

Securing the Message Bus with Kafka Streams | Paul Otto and Ryan Salcido, Raf...

Kafka Summit NYC 2017 - Data Processing at LinkedIn with Apache Kafka

Powering an API with GraphQL, Golang, and NoSQL

Flink Forward San Francisco 2019: Developing and operating real-time applicat...

InfluxData Internals by Ryan Betts

Case Study: Stream Processing on AWS using Kappa Architecture

Administrative techniques to reduce Kafka costs | Anna Kepler, Viasat

HBaseCon2017 Apache HBase at Didi

Flink forward SF 2017: Elizabeth K. Joseph and Ravi Yadav - Flink meet DC/OS ...

Flink Forward Berlin 2017: Steffen Hausmann - Build a Real-time Stream Proces...

Similar to How Mapbox Scales over 9 AWS Regions

Mapbox.com: Serving maps from 8 regions

Johan

eHarmony in the Cloud

Craig Dickson

Amazon Web Services Architecture - An Overview

Scott Weber

Sabre presentation for MySQL user conference 2004

Alan Walker

MCSA 70-412 Chapter 05

Computer Networking

Getting Started with Hadoop

Cloudera, Inc.

سکوهای ابری و مدل های برنامه نویسی در ابر

datastack

REDSHIFT - Amazon

Douglas Bernardini

AWS re:Invent 2013 Recap

Barry Jones

Hadoop ppt on the basics and architecture

saipriyacoool

Apache Geode Meetup, London

Apache Geode

Big data on aws

Serkan Özal

Streaming sql and druid

arupmalakar

Hadoop 3.0 - Revolution or evolution?

Uwe Printz

In-memory Caching in HDFS: Lower Latency, Same Great Taste

DataWorks Summit

SQL To NoSQL - Top 6 Questions Before Making The Move

IBM Cloud Data Services

Distributed Logging Architecture in the Container Era

Glenn Davis

MySQL in the Hosted Cloud

Colin Charles

Managing storage on Prem and in Cloud

Howard Marks

Enterprise Holding’s first started with Hadoop as a POC in 2013. Today, we have clusters on premises and in the cloud. This talk will explore our experience with Big Data and outline three common big data architectures (batch, lambda, and kappa). Then, we’ll dive into the decision points to necessary for your own cluster, for example: cloud vs on premises, physical vs virtual, workload, and security. These decisions will help you understand what direction to take. Finally, we’ll share some lessons learned with the pieces of our architecture worked well and rant about those which didn’t. No deep Hadoop knowledge is necessary, architect or executive level.

Innovation in the Data Warehouse - StampedeCon 2016

StampedeCon

Similar to How Mapbox Scales over 9 AWS Regions (20)

Mapbox.com: Serving maps from 8 regions

eHarmony in the Cloud

Amazon Web Services Architecture - An Overview

Sabre presentation for MySQL user conference 2004

MCSA 70-412 Chapter 05

Getting Started with Hadoop

سکوهای ابری و مدل های برنامه نویسی در ابر

REDSHIFT - Amazon

AWS re:Invent 2013 Recap

Hadoop ppt on the basics and architecture

Apache Geode Meetup, London

Big data on aws

Streaming sql and druid

Hadoop 3.0 - Revolution or evolution?

In-memory Caching in HDFS: Lower Latency, Same Great Taste

SQL To NoSQL - Top 6 Questions Before Making The Move

Distributed Logging Architecture in the Container Era

MySQL in the Hosted Cloud

Managing storage on Prem and in Cloud

Innovation in the Data Warehouse - StampedeCon 2016

Recently uploaded

Effective data discovery is crucial for maintaining compliance and mitigating risks in today's rapidly evolving privacy landscape. However, traditional manual approaches often struggle to keep pace with the growing volume and complexity of data. Join us for an insightful webinar where industry leaders from TrustArc and Privya will share their expertise on leveraging AI-powered solutions to revolutionize data discovery. You'll learn how to: - Effortlessly maintain a comprehensive, up-to-date data inventory - Harness code scanning insights to gain complete visibility into data flows leveraging the advantages of code scanning over DB scanning - Simplify compliance by leveraging Privya's integration with TrustArc - Implement proven strategies to mitigate third-party risks Our panel of experts will discuss real-world case studies and share practical strategies for overcoming common data discovery challenges. They'll also explore the latest trends and innovations in AI-driven data management, and how these technologies can help organizations stay ahead of the curve in an ever-changing privacy landscape.

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

TrustArc

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Accelerating FinTech Innovation: Unleashing API Economy and GenAI Vasa Krishnan, Chief Technology Officer - FinResults Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

apidays

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Zilliz

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

Scalable LLM APIs for AI and Generative AI Application Development Ettikan Karuppiah, Director/Technologist - NVIDIA Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Scalable LLM APIs for AI and Generative AI Applicati...

apidays

Building Digital Trust in a Digital Economy Veronica Tan, Director - Cyber Security Agency of Singapore Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

apidays

Created by Mozilla Research in 2012 and now part of Linux Foundation Europe, the Servo project is an experimental rendering engine written in Rust. It combines memory safety and concurrency to create an independent, modular, and embeddable rendering engine that adheres to web standards. Stewardship of Servo moved from Mozilla Research to the Linux Foundation in 2020, where its mission remains unchanged. After some slow years, in 2023 there has been renewed activity on the project, with a roadmap now focused on improving the engine’s CSS 2 conformance, exploring Android support, and making Servo a practical embeddable rendering engine. In this presentation, Rakhi Sharma reviews the status of the project, our recent developments in 2023, our collaboration with Tauri to make Servo an easy-to-use embeddable rendering engine, and our plans for the future to make Servo an alternative web rendering engine for the embedded devices industry. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://ossna2024.sched.com/event/1aBNF/a-year-of-servo-reboot-where-are-we-now-rakhi-sharma-igalia

A Year of the Servo Reboot: Where Are We Now?

Igalia

"I see eyes in my soup": How Delivery Hero implemented the safety system for ...

Zilliz

In the thrilling conclusion to 2023, ransomware groups had a banner year, really outdoing themselves in the "make everyone's life miserable" department. LockBit 3.0 took gold in the hacking olympics, followed by the plucky upstarts Clop and ALPHV/BlackCat. Apparently, 48% of organizations were feeling left out and decided to get in on the cyber attack action. Business services won the "most likely to get digitally mugged" award, with education and retail nipping at their heels. Hackers expanded their repertoire beyond boring old encryption to the much more exciting world of extortion. The US, UK and Canada took top honors in the "countries most likely to pay up" category. Bitcoins were the currency of choice for discerning hackers, because who doesn't love untraceable money?

Ransomware_Q4_2023. The report. [EN].pdf

Overkill Security

As privacy and data protection regulations evolve rapidly, organizations operating in multiple jurisdictions face mounting challenges to ensure compliance and safeguard customer data. With state-specific privacy laws coming up in multiple states this year, it is essential to understand what their unique data protection regulations will require clearly. How will data privacy evolve in the US in 2024? How to stay compliant? Our panellists will guide you through the intricacies of these states' specific data privacy laws, clarifying complex legal frameworks and compliance requirements. This webinar will review: - The essential aspects of each state's privacy landscape and the latest updates - Common compliance challenges faced by organizations operating in multiple states and best practices to achieve regulatory adherence - Valuable insights into potential changes to existing regulations and prepare your organization for the evolving landscape

TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments

TrustArc

Architecting Cloud Native Applications

WSO2

MS Copilot expands with MS Graph connectors

Nanddeep Nachan

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

apidays

In this session, we will delve into strategic approaches for optimizing knowledge management within Microsoft 365, amidst the evolving landscape of Copilot. From leveraging automatic metadata classification and permission governance with SharePoint Premium, to unlocking Viva Engage for the cultivation of knowledge and communities, you will gain actionable insights to bolster your organization's knowledge-sharing initiatives. In this session, we will also explore how to facilitate solutions to enable your employees to find answers and expertise within Microsoft 365. You will leave equipped with practical techniques and a deeper understanding of how there is more to effective knowledge management than just enabling Copilot, but building actual solutions to prepare the knowledge that Copilot and your employees can use.

Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...

Drew Madelung

Boost Fertility New Invention Ups Success Rates.pdf

sudhanshuwaghmare1

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

sammart93

This presentations targets students or working professionals. You may know Google for search, YouTube, Android, Chrome, and Gmail, but did you know Google has many developer tools, platforms & APIs? This comprehensive yet still high-level overview outlines the most impactful tools for where to run your code, store & analyze your data. It will also inspire you as to what's possible. This talk is 50 minutes in length.

Powerful Google developer tools for immediate impact! (2023-24 C)

wesley chun

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

Recently uploaded (20)

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

How to Troubleshoot Apps for the Modern Connected Worker

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Apidays Singapore 2024 - Scalable LLM APIs for AI and Generative AI Applicati...

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

A Year of the Servo Reboot: Where Are We Now?

"I see eyes in my soup": How Delivery Hero implemented the safety system for ...

Ransomware_Q4_2023. The report. [EN].pdf

TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments

Architecting Cloud Native Applications

MS Copilot expands with MS Graph connectors

Apidays New York 2024 - The value of a flexible API Management solution for O...

Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...

Boost Fertility New Invention Ups Success Rates.pdf

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Powerful Google developer tools for immediate impact! (2023-24 C)

AWS Community Day CPH - Three problems of Terraform

Data Cloud, More than a CDP by Matt Robison

How Mapbox Scales over 9 AWS Regions

1. How Mapbox Scales Over 9 Data Centers Johan @freenerd johan@mapbox.com Madrid DevOps November 2015 1

2. • What is Mapbox? • 9 data centers? • Tracing a map request 2

3. 3

4. 4

5. 5

6. 6

7. • What is Mapbox? • 9 Data Centers? • Tracing a map request 7

8. 9 Data Centers? 8

9. 9

10. 10

11. 9 Data Centers? • Why run this in many regions? • One region = cheaper, less complex, easier to build and maintain 11

12. 9 Data Centers? • Global high availability • Global low latency 12

13. 9 Data Centers? Global high availability 13

14. 9 Data Centers? Global high availability • Mapbox is critical infrastructure for our customers • Mapbox SLA: 99.9% • Problems for high availability • AWS problems • Mapbox software or conﬁguration problems • Critical deploys 14

15. 9 Data Centers? • Global high availability • Global low latency 15

16. 9 Data Centers? Global low latency 16

17. 9 Data Centers? Global low latency • Can't beat the speed of light • Latency is critical for using a map • Bring our data closer to our users 17

18. 9 Data Centers? • Global high availability • Global low latency 18

19. Let's trace a request 19

20. 20

21. 21

22. What is a map? 22

23. 23

24. • Grid over the world • Every cell of the grid is a tile • Different zoomlevels • Zoomlevel 0 is the world • Zoomlevel 13 is a city • Every tile is identiﬁed by mapid, coordinates and zoomlevel 24

25. 25

26. Client • Browser loads Javascript • Mapbox.js allows for customizing map with very few lines • Javascript • Determine viewport • Request each individual tile 26

27. Client https://tiles.mapbox.com/v4/ map.id/17/70428/42997.png?access_token=pk.xxx 27

28. 28

29. CDN • Content Distribution Network • Physical cache close to users • AWS: Cloudfront • Others: Akamai, Fastly, CloudFlare 29

30. CDN 30

31. CDN • When a request comes in: • Find nearest edge location • Terminate TLS • Match request to behaviour • Look in cache (based on URL & Query String) • If object is there: return 31

32. CDN • Your CDN works best if it can serve everything from cache • How to remove stale data? • Trade-off: high cache hit rate vs. update delay • Time-To-Live when a cached object expires • We use 5 minutes • 35 % cache hit rate 32

33. 33

34. DNS • Originally: Resolve domain names to IP addresses • Also: Route request to nearest data center • best region for request based historic on latency • Amazon: Route53 • Others: Dyn, easyDNS, Akamai 34

35. DNS 35

36. 36

37. Load Balancer • Route requests to application servers • Entry point to a region • AWS: Elastic Load Balancer (ELB) • Others: haproxy, nginx, f5 37

38. Load Balancer • Terminate TLS • Determine which application server to route to • Healthy server • ELB: Server with least outstanding requests • Wait for results and return 38

39. 39

40. Application Servers • Virtual Machines • AWS: Elastic Compute Cloud (EC2) • Others: Google Compute Cloud, Rackspace, Digital Ocean 40

41. Application Servers • c3.xlarge instances • Ubuntu Linux • Node.js/Express 41

42. Application Servers • Authenticate • Load map data • Fetch tile and return 42

43. 43

44. DynamoDB • Primary/Replica • Reads to replicas, writes only to primary • Replicas only in 2 regions • Reads for non-replica regions need to go over the Internet • In-instance caching of authentication/map information 1 https://www.mapbox.com/blog/scaling-the-mapbox-infrastructure-with- dynamodb-streams/ 44

45. 45

46. Application Servers Fetch tiles • check simultanously in cache (redis) and object store (s3) • return from where is found ﬁrst • if only found in object store, update local cache 46

47. Application Servers • redis is used as least-recently used cache, thus popular tiles for a region are usually cached • s3 is slow, because data is in us-east-1 bucket only • Stats: • 80% cache hits • r3.4xlarge with 122 GB of memory 47

48. 48

49. 49

50. From 2 to 9 regions 50

51. From 2 to 9 regions 51

52. From 2 to 9 regions 52

53. Thanks • What is Mapbox? • 9 Data Centers? • Tracing a Map Request @freenerd johan@mapbox.com 53

54. http://geodevelopers.org/ 54

55. Elasticity • EC2 instances are provisioned via Auto Scaling Group • Auto Scaling is based on instance CPU load • Scale up/down if CPU load over/under 55%/20% for 2 minutes 55

56. 56

How Mapbox Scales over 9 AWS Regions

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to How Mapbox Scales over 9 AWS Regions

Similar to How Mapbox Scales over 9 AWS Regions (20)

More from Johan

More from Johan (13)

Recently uploaded

Recently uploaded (20)

How Mapbox Scales over 9 AWS Regions