Content Delivery Networks (CDNs) improve user experience by reducing latency, packet loss, and jitter. They also increase scalability and fault tolerance. FirstPoint is a traffic management system that directs users to optimal mirrored websites. It uses topology discovery to cluster nameservers and importance sampling for congestion measurement to map users to the closest mirrors.
(NET308) Consolidating DNS Data in the Cloud with Amazon Route 53Amazon Web Services
In this session, we show you how to use Amazon Route 53 to consolidate your DNS data and manage it centrally. Learn how to use Amazon Route 53 for public DNS and for private DNS in VPC, and also learn how to combine Amazon Route 53 private DNS with your own DNS infrastructure.
Riding the Stream Processing Wave (Strange loop 2019)Samarth Shetty
At LinkedIn, we run several thousands of stream processing applications which, coupled with our scale, has exposed us to some unique challenges. We will talk about the 3 kinds of applications that have made the most impact on our stream processing platform.
At SandCamp 2011, Brandon Lyon spoke about Performance & Scalability for Drupal websites. Unlike most Performance & Scalability talks he didn't just talk about the different resources available to enhance your site, but also gave instructions on how to identify the problem areas on your site as well. Brandon covered everything from the many layers of caching, to optimizing PHP, Apache, and MySQL and how to measure the performance of each in the following presentation.
This webinar will cover best practices around dev/ops and general operations for those already familiar with basics of MongoDB. Topics will include team roles around data model design, monitoring, hardware configurations, replication and horizontal scaling.
This presentation explains how to deploy and use the Integrated Caching feature on Netscaler. I gave this presentation to Citrix staff, customers and partners in worldwide in 2011. The presentation covers best practices and gotchas :) Integrated Caching is an excellent feature that can greatly improve the performance of your website.
AWS Summit London 2014 | Dynamic Content Acceleration (300)Amazon Web Services
This session is recommended for people who are new to content distribution networks (CDNs) and have a need to decrease server load and speed up their website’s load time.
In this mid-level technical session you will be able to learn more about improving the performance of web sites and web applications using Amazon CloudFront and Amazon Router 53. Learn how to assess whether your web applications will benefit from caching and how to optimize the delivery of static and dynamic content to boost performance and improve your customers' experience in using your applications.
(NET308) Consolidating DNS Data in the Cloud with Amazon Route 53Amazon Web Services
In this session, we show you how to use Amazon Route 53 to consolidate your DNS data and manage it centrally. Learn how to use Amazon Route 53 for public DNS and for private DNS in VPC, and also learn how to combine Amazon Route 53 private DNS with your own DNS infrastructure.
Riding the Stream Processing Wave (Strange loop 2019)Samarth Shetty
At LinkedIn, we run several thousands of stream processing applications which, coupled with our scale, has exposed us to some unique challenges. We will talk about the 3 kinds of applications that have made the most impact on our stream processing platform.
At SandCamp 2011, Brandon Lyon spoke about Performance & Scalability for Drupal websites. Unlike most Performance & Scalability talks he didn't just talk about the different resources available to enhance your site, but also gave instructions on how to identify the problem areas on your site as well. Brandon covered everything from the many layers of caching, to optimizing PHP, Apache, and MySQL and how to measure the performance of each in the following presentation.
This webinar will cover best practices around dev/ops and general operations for those already familiar with basics of MongoDB. Topics will include team roles around data model design, monitoring, hardware configurations, replication and horizontal scaling.
This presentation explains how to deploy and use the Integrated Caching feature on Netscaler. I gave this presentation to Citrix staff, customers and partners in worldwide in 2011. The presentation covers best practices and gotchas :) Integrated Caching is an excellent feature that can greatly improve the performance of your website.
AWS Summit London 2014 | Dynamic Content Acceleration (300)Amazon Web Services
This session is recommended for people who are new to content distribution networks (CDNs) and have a need to decrease server load and speed up their website’s load time.
In this mid-level technical session you will be able to learn more about improving the performance of web sites and web applications using Amazon CloudFront and Amazon Router 53. Learn how to assess whether your web applications will benefit from caching and how to optimize the delivery of static and dynamic content to boost performance and improve your customers' experience in using your applications.
In this presentation, created for a webinar recorded on 4/26/2012, we demo'd Amazon Route 53's new Latency Based Routing (LBR) feature. LBR is one of Amazon Route 53’s most requested features and helps improve your application’s performance for a global audience. LBR works by routing your customers to the AWS endpoint (e.g. EC2 instances, Elastic IPs or ELBs) that provides the fastest experience based on actual performance measurements of the different AWS regions where your application is running.
Today's high-traffic web sites must implement performance-boosting measures that reduce data processing and reduce load on the database, while increasing the speed of content delivery. One such method is the use of a cache to temporarily store whole pages, database recordsets, large objects, and sessions. While many caching mechanisms exist, memcached provides one of the fastest and easiest-to-use caching servers. Coupling memcached with the alternative PHP cache (APC) can greatly improve performance by reducing data processing time. In this talk, Ben Ramsey covers memcached and the pecl/memcached and pecl/apc extensions for PHP, exploring caching strategies, a variety of configuration options to fine-tune your caching solution, and discusses when it may be appropriate to use memcached vs. APC to cache objects or data.
BigBase is a read-optimized version of HBase NoSQL data store and is FULLY, 100% HBase compatible. 100% compatibility means that the upgrade from HBase to BigBase and other way around does not involve data migration and even can be made without stopping the cluster (via rolling restart).
At Salesforce, we have deployed many thousands of HBase/HDFS servers, and learned a lot about tuning during this process. This talk will walk you through the many relevant HBase, HDFS, Apache ZooKeeper, Java/GC, and Operating System configuration options and provides guidelines about which options to use in what situation, and how they relate to each other.
AWS re:Invent 2016: Deep Dive on Amazon Elastic Block Store (STG301)Amazon Web Services
In this popular session, you will learn about the latest features and use cases for Amazon EBS, including best practices, an overview of newly introduced features, and brand-new re:Invent announcements. In particular we will cover the expanded portoflio of volume types, including provisioned IOPS, cold storage, and throughput-optimized. This session will help database admins and application architects understand how to blend performance and cost with applicaitns for big data analytics, data warehousing, and transactional and NoSQL databases.
In this presentation, created for a webinar recorded on 4/26/2012, we demo'd Amazon Route 53's new Latency Based Routing (LBR) feature. LBR is one of Amazon Route 53’s most requested features and helps improve your application’s performance for a global audience. LBR works by routing your customers to the AWS endpoint (e.g. EC2 instances, Elastic IPs or ELBs) that provides the fastest experience based on actual performance measurements of the different AWS regions where your application is running.
Today's high-traffic web sites must implement performance-boosting measures that reduce data processing and reduce load on the database, while increasing the speed of content delivery. One such method is the use of a cache to temporarily store whole pages, database recordsets, large objects, and sessions. While many caching mechanisms exist, memcached provides one of the fastest and easiest-to-use caching servers. Coupling memcached with the alternative PHP cache (APC) can greatly improve performance by reducing data processing time. In this talk, Ben Ramsey covers memcached and the pecl/memcached and pecl/apc extensions for PHP, exploring caching strategies, a variety of configuration options to fine-tune your caching solution, and discusses when it may be appropriate to use memcached vs. APC to cache objects or data.
BigBase is a read-optimized version of HBase NoSQL data store and is FULLY, 100% HBase compatible. 100% compatibility means that the upgrade from HBase to BigBase and other way around does not involve data migration and even can be made without stopping the cluster (via rolling restart).
At Salesforce, we have deployed many thousands of HBase/HDFS servers, and learned a lot about tuning during this process. This talk will walk you through the many relevant HBase, HDFS, Apache ZooKeeper, Java/GC, and Operating System configuration options and provides guidelines about which options to use in what situation, and how they relate to each other.
AWS re:Invent 2016: Deep Dive on Amazon Elastic Block Store (STG301)Amazon Web Services
In this popular session, you will learn about the latest features and use cases for Amazon EBS, including best practices, an overview of newly introduced features, and brand-new re:Invent announcements. In particular we will cover the expanded portoflio of volume types, including provisioned IOPS, cold storage, and throughput-optimized. This session will help database admins and application architects understand how to blend performance and cost with applicaitns for big data analytics, data warehousing, and transactional and NoSQL databases.
AWS re:Invent 2016: From Resilience to Ubiquity - #NetflixEverywhere Global A...Amazon Web Services
Building and evolving a pervasive, global service requires a multi-disciplined approach that balances requirements with service availability, latency, data replication, compute capacity, and efficiency. In this session, we’ll follow the Netflix journey of failure, innovation, and ubiquity. We'll review the many facets of globalization and then delve deep into the architectural patterns that enable seamless, multi-region traffic management; reliable, fast data propagation; and efficient service infrastructure. The patterns presented will be broadly applicable to internet services with global aspirations.
AWS re:Invent 2016: Amazon CloudFront Flash Talks: Best Practices on Configur...Amazon Web Services
In this series of 15-minute technical flash talks you will learn directly from Amazon CloudFront engineers and their best practices on debugging caching issues, measuring performance using Real User Monitoring (RUM), and stopping malicious viewers using CloudFront and AWS WAF.
Peng Kang, Software Engineer, Dropbox + Richi Gupta, Engineering Manager, Dropbox
As a scalable and reliable data streaming solution with a rich ecosystem, Kafka is widely adopted in Dropbox infrastructure in various scenarios. It is part of Dropbox’s analytics data pipeline, stream processing platform and more mission critical systems. Jetstream is the team that provides Kafka as a service in Dropbox infrastructure. We manage the clusters, develop tooling, and enforce policies, so that our users can enjoy a highly available and reliable service. In this talk, we will share our experiences and learnings running Kafka clusters, pipelines that enable high durability (direct writes to kafka) and availability (goscribe), the policies we enforce for high reliability, the tooling we have for maintenance and stress testing, and finally an overview of Dropbox’s next generation queueing service built on top Kafka.
https://www.meetup.com/KafkaBayArea/events/266327152/
Cloud Architecture Tutorial - Running in the Cloud (3of3)Adrian Cockcroft
Part 3 of the talk covers how to transition to cloud, how to bootstrap developers, how to run cloud services including Cassandra, capacity planning and workload analysis, and organizational structure
Kafka is a high-throughput, fault-tolerant, scalable platform for building high-volume near-real-time data pipelines. This presentation is about tuning Kafka pipelines for high-performance.
Select configuration parameters and deployment topologies essential to achieve higher throughput and low latency across the pipeline are discussed. Lessons learned in troubleshooting and optimizing a truly global data pipeline that replicates 100GB data under 25 minutes is discussed.
More Nines for Your Dimes: Improving Availability and Lowering Costs using Au...Amazon Web Services
Running your Amazon EC2 instances in Auto Scaling groups allows you to improve your application's availability right out of the box. Auto Scaling replaces impaired or unhealthy instances automatically to maintain your desired number of instances (even if that number is one). You can also use Auto Scaling to automate the provisioning of new instances and software configurations as well as to track of usage and costs by app, project, or cost center. Of course, you can also use Auto Scaling to adjust capacity as needed - on demand, on a schedule, or dynamically based on demand. In this session, we show you a few of the tools you can use to enable Auto Scaling for the applications you run on Amazon EC2.
(A talk given at Wix R&D in Dnipro, Ukraine on March 2017. Video available at https://www.youtube.com/watch?v=eIX33mQdkAI&feature=youtu.be)
While microservices are conceptually simple, it's a deep rabbit hole to go down. Deceptively simple questions can have far-reaching implications: Which communication protocol should I choose? Is event-driven the way to go? What monitoring tools should I put in place?
In this talk we'll cover some of the fundamental questions, outline the solutions adopted or developed by Wix, and share our hindsight on what worked well for us, what didn't and thoughts on future directions for our stack.
More Nines for Your Dimes: Improving Availability and Lowering Costs using Au...Amazon Web Services
Running your Amazon EC2 instances in Auto Scaling groups allows you to improve your application's availability right out of the box. Auto Scaling replaces impaired or unhealthy instances automatically to maintain your desired number of instances (even if that number is one). You can also use Auto Scaling to automate the provisioning of new instances and software configurations as well as to track of usage and costs by app, project, or cost center. Of course, you can also use Auto Scaling to adjust capacity as needed - on demand, on a schedule, or dynamically based on demand. In this session, we show you a few of the tools you can use to enable Auto Scaling for the applications you run on Amazon EC2. We also share tips and tricks we've picked up from customers such as Netflix, Adobe, Nokia, and Amazon.com about managing capacity, balancing performance against cost, and optimizing availability.
This tutorial gives out an brief and interesting introduction to modern stream computing technologies. The participants can learn the essential concepts and methodologies for designing and building a advanced stream processing system. The tutorial unveils the key fundamentals behind various kinds of design choices. Some forecast of technology developments in this domain is also introduced at the last section of this tutorial.
Sharing is Caring: Toward Creating Self-tuning Multi-tenant Kafka (Anna Povzn...HostedbyConfluent
Deploying Kafka to support multiple teams or even an entire company has many benefits. It reduces operational costs, simplifies onboarding of new applications as your adoption grows, and consolidates all your data in one place. However, this makes applications sharing the cluster vulnerable to any one or few of them taking all cluster resources. The combined cluster load also becomes less predictable, increasing the risk of overloading the cluster and data unavailability.
In this talk, we will describe how to use quota framework in Apache Kafka to ensure that a misconfigured client or unexpected increase in client load does not monopolize broker resources. You will get a deeper understanding of bandwidth and request quotas, how they get enforced, and gain intuition for setting the limits for your use-cases.
While quotas limit individual applications, there must be enough cluster capacity to support the combined application load. Onboarding new applications or scaling the usage of existing applications may require manual quota adjustments and upfront capacity planning to ensure high availability.
We will describe the steps we took toward solving this problem in Confluent Cloud, where we must immediately support unpredictable load with high availability. We implemented a custom broker quota plugin (KIP-257) to replace static per broker quota allocation with dynamic and self-tuning quotas based on the available capacity (which we also detect dynamically). By learning our journey, you will have more insights into the relevant problems and techniques to address them.
Как сделать высоконагруженный сервис, не зная количество нагрузки / Олег Обле...Ontico
Существует множество архитектур и способов масштабирования систем. Сегодня многие компании мигрируют в облачные сервисы или используют контейнеры. Но действительно ли это так необходимо и нужно ли следовать трендам?
В данном докладе мне бы хотелось рассказать об архитектуре, которую я спланировал и внедрил в компании InnoGames. Архитектура, не требующая вмешательства администратора в случае лавинообразного увеличения нагрузки и, что ещё более важно, умеющая редуцироваться в случае отсутствия её для экономии затрат.
Вы узнаете об опыте создания сервиса с очень непростыми критериями и поймёте, что не обязательно платить в 3 раза дороже за AWS или любую подобную систему.
- Что такое CRM. Зачем нам этот сервис.
- Инфраструктура.
-- Graphite. Почему он должен быть надежным и быстрым.
-- Puppet + gitlab.
-- Балансировка нагрузки.
-- Наше облако. Зачем нам openstack, когда есть serveradmin!? Как роль сервера определяется несколькими атрибутами в веб-интерфейсе.
-- Nagios + аггрегаторы. Другой взгляд на то, как мониторить сервисы через Graphite.
-- Мониторинг кластеров. Clusterhc и Grafsy.
-- Brassmonkey. Как мы написали своего сисадмина на python.
-- Бэкапы.
- Архитектура CRM3.
- Autoscaling или как проанализировать кучу данных и принять решения.
Cloud Connected Devices on a Global Scale (CPN303) | AWS re:Invent 2013Amazon Web Services
Increasingly, mobile and other connected devices are leveraging the scalability and capabilities of the cloud to deliver services to end users. However, connecting these devices to the cloud presents unique challenges. Resource constraints make it impossible to use many common frameworks and transport restrictions make it difficult to use dynamic cloud resources. In this session, learn how you can develop and deploy highly-scalable global solutions using Amazon Web Services (Amazon Virtual Private Cloud, Elastic IP addresses, Amazon Route 53, Auto Scaling) and tools like Puppet. Hear how Panasonic and Banjo architect their cloud infrastructure from both a start-up and enterprise perspective.
This 7-second Brain Wave Ritual Attracts Money To You.!nirahealhty
Discover the power of a simple 7-second brain wave ritual that can attract wealth and abundance into your life. By tapping into specific brain frequencies, this technique helps you manifest financial success effortlessly. Ready to transform your financial future? Try this powerful ritual and start attracting money today!
1.Wireless Communication System_Wireless communication is a broad term that i...JeyaPerumal1
Wireless communication involves the transmission of information over a distance without the help of wires, cables or any other forms of electrical conductors.
Wireless communication is a broad term that incorporates all procedures and forms of connecting and communicating between two or more devices using a wireless signal through wireless communication technologies and devices.
Features of Wireless Communication
The evolution of wireless technology has brought many advancements with its effective features.
The transmitted distance can be anywhere between a few meters (for example, a television's remote control) and thousands of kilometers (for example, radio communication).
Wireless communication can be used for cellular telephony, wireless access to the internet, wireless home networking, and so on.
Multi-cluster Kubernetes Networking- Patterns, Projects and GuidelinesSanjeev Rampal
Talk presented at Kubernetes Community Day, New York, May 2024.
Technical summary of Multi-Cluster Kubernetes Networking architectures with focus on 4 key topics.
1) Key patterns for Multi-cluster architectures
2) Architectural comparison of several OSS/ CNCF projects to address these patterns
3) Evolution trends for the APIs of these projects
4) Some design recommendations & guidelines for adopting/ deploying these solutions.
ER(Entity Relationship) Diagram for online shopping - TAEHimani415946
https://bit.ly/3KACoyV
The ER diagram for the project is the foundation for the building of the database of the project. The properties, datatypes, and attributes are defined by the ER diagram.
5. Why does my click not workWhy does my click not work
• Latency - Browser takes a long timeLatency - Browser takes a long time
to load the pageto load the page
• Packet Loss - Browser hangs, userPacket Loss - Browser hangs, user
needs to hit refreshneeds to hit refresh
• Jitter - Streams are jerkyJitter - Streams are jerky
• Server load - Browser connects butServer load - Browser connects but
does not fully load the pagedoes not fully load the page
• Broken/missing contentBroken/missing content
6. The Akamai SolutionThe Akamai Solution
Servers
at Network Edge
Content
Providers
End
Users
NAP
NAP
7. 3
Content Provider’s
Web Server
DNS
WWW.XYZ.COM1
Downloading www.xyz.comDownloading www.xyz.com
- before CDNs- before CDNs
• User enters www.xyz.comUser enters www.xyz.com
• Browser requests IPBrowser requests IP
address for www.xyz.comaddress for www.xyz.com
• Browser requestsBrowser requests
embedded objectsembedded objects
• Content provider’s webContent provider’s web
server returns HTMLserver returns HTML
10.10.123.82
• Browser requests HTMLBrowser requests HTML
• DNS returns IP addressDNS returns IP address
4
7
6
• Browser obtains IP addresses forBrowser obtains IP addresses for
hostnames listed in URLs of objectshostnames listed in URLs of objects
embedded on pageembedded on page
• Content provider’s web serverContent provider’s web server
returns embedded objectsreturns embedded objects
10.10.123.8
5
9. Origin - Content
Provider’s Web
Server
Delivery of Whole SiteDelivery of Whole Site
66
6. Browser obtains content6. Browser obtains content
from optimal Akamai serverfrom optimal Akamai server
WWW.XYZ.COMWWW.XYZ.COM
DNS
1. Browser requests DNS for IP1. Browser requests DNS for IP
of www.xyz.comof www.xyz.com
11
33
3. DNS returns IP of optimal3. DNS returns IP of optimal
Akamai serverAkamai server
5. Akamai server assembles5. Akamai server assembles
page, contacting origin aspage, contacting origin as
neededneeded
55
4. Browser requests Akamai4. Browser requests Akamai
server for contentserver for content
44
2. DNS follows CNAME redirect2. DNS follows CNAME redirect
to www.xyz.edgesuite.netto www.xyz.edgesuite.net
22
10. Delivery of Whole Site - DNSDelivery of Whole Site - DNS
RedirectRedirect
DNS CNAME RECORDDNS CNAME RECORD
www.xyz.com CNAME www.xyz.edgesuite.net 2Dwww.xyz.com CNAME www.xyz.edgesuite.net 2D
11. Delivery of Whole Site - PageDelivery of Whole Site - Page
AssemblyAssembly
Site owners create
container pages that
can be populated
with varying content
Container Page
[TTL=5d]
[XYZ news, content,
promotions, etc.
TTL=5d]
[Breaking headlines
TTL=2h]
[TTL=15m]
[TTL=8h]
13. OutlineOutline
• CDNs - Review of mechanicsCDNs - Review of mechanics
• FirstPoint - Traffic Management forFirstPoint - Traffic Management for
mirrored websitesmirrored websites
14. What is FirstPointWhat is FirstPoint
• Traffic management system forTraffic management system for
mirrored websitesmirrored websites
• Directs browser to the optimal mirrorDirects browser to the optimal mirror
• DNS basedDNS based
• Application level anycastApplication level anycast
15. Why FirstPointWhy FirstPoint
• Content providers have mirroredContent providers have mirrored
websiteswebsites
• Content providers only want toContent providers only want to
offload embedded contentoffload embedded content
- ControlControl
- SecuritySecurity
- PerformancePerformance
17. What is the Mapping ProblemWhat is the Mapping Problem
• Problem of directing requests toProblem of directing requests to
servers so as to optimize end-userservers so as to optimize end-user
experienceexperience
- reduce latencyreduce latency
- reduce lossreduce loss
- reduce jitterreduce jitter
• Assumption - servers are fineAssumption - servers are fine
• Applicable to 2 mirrors or 1500Applicable to 2 mirrors or 1500
Akamai locationsAkamai locations
18. AttemptAttempt
• Measure which is closerMeasure which is closer
- Closeness changes over timeCloseness changes over time
• Measure frequentlyMeasure frequently
- Bothers peopleBothers people
- Too many to doToo many to do
~500,000 unique nameservers on any given day
10 sec per measurement cycle
19. IdeaIdea
• TopologyTopology
- relatively staticrelatively static
- changes in BGP timechanges in BGP time
- order of hours if not daysorder of hours if not days
• CongestionCongestion
- dynamicdynamic
- changes in round-trip timechanges in round-trip time
- order of millisecondsorder of milliseconds
21. AliasingAliasing
• Router fabrics using HSRP (hotRouter fabrics using HSRP (hot
stand-by routing protocol)stand-by routing protocol)
- correlate over timecorrelate over time
• Routers with multiple interfacesRouters with multiple interfaces
- source address of UDP/ICMP packetssource address of UDP/ICMP packets
22. Set coverSet cover
• Let sets represent proxy pointsLet sets represent proxy points
• Let elements represent nameserversLet elements represent nameservers
• Find minimum collection of proxyFind minimum collection of proxy
points covering nameserverspoints covering nameservers
X covers 1, 2, 3 and 4X covers 1, 2, 3 and 4
X
1 2 3 4
23. Topology DiscoveryTopology Discovery
• At each mirror maintain list of partial paths toAt each mirror maintain list of partial paths to
nameserversnameservers
• At each epoch extend paths by 1, inAt each epoch extend paths by 1, in
randomized fashion, and exchange with otherrandomized fashion, and exchange with other
mirrormirror
• If the two (partial) paths to a namerver haveIf the two (partial) paths to a namerver have
intersected then declare that nameserverintersected then declare that nameserver
done.done.
• If path has reached forbidden IP then waitIf path has reached forbidden IP then wait
• Use pair of proxies in case of failureUse pair of proxies in case of failure
26. Histogram of cluster sizesHistogram of cluster sizes
HISTOGRAM
0
5000
10000
15000
20000
25000
30000
35000
1 2 3 4 5 6-99 100-999 1000-
5999
6000-
Cluster Size
Number
27. Congestion MeasurementCongestion Measurement
Problem - Still too many measurements to do.Problem - Still too many measurements to do.
90,000 measurements every 10s with 32B90,000 measurements every 10s with 32B
packets requires a few Mbps per mirror.packets requires a few Mbps per mirror.
Solution - Importance based samplingSolution - Importance based sampling
28. CDF of End-user LoadCDF of End-user Load
CDF
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
Number of Clusters
Load
29. Load EstimationLoad Estimation
500,000 nameservers500,000 nameservers
reduced toreduced to
90,000 clusters90,000 clusters
7,000 account for 95% end-user load!7,000 account for 95% end-user load!
30. Mapping Problem - Solved!Mapping Problem - Solved!
Maps built every 10s
31. FirstPointFirstPoint
• Customers - how to tell?Customers - how to tell?
- look for CNAME to akadns.netlook for CNAME to akadns.net
• Customers - who?Customers - who?
- High traffic content providersHigh traffic content providers
- Yahoo!, Microsoft, TicketMaster etcYahoo!, Microsoft, TicketMaster etc
• Price - don’t ask :)Price - don’t ask :)
• Competitors - whoCompetitors - who
- one-of-a-kind serviceone-of-a-kind service
- boxes: Cisco, F5, Foundryboxes: Cisco, F5, Foundry
32. FirstPoint - other aspectsFirstPoint - other aspects
• Load-balancingLoad-balancing
- estimate-basedestimate-based
- feedback-based : https, snmpfeedback-based : https, snmp
- cost-based: 95/5cost-based: 95/5
• Fast cutout in case of failoverFast cutout in case of failover
• Highly fault-tolerantHighly fault-tolerant
- hardware duplication, leader electionhardware duplication, leader election
- overlay routing, BGP-based anycastoverlay routing, BGP-based anycast
• Integration with other servicesIntegration with other services
- DOS/Load failoverDOS/Load failover
35. Patents (pending)Patents (pending)
• Global load balancing across mirrored data centers.Global load balancing across mirrored data centers.
Utility # 20020129134Utility # 20020129134
• Method for predicting file download time fromMethod for predicting file download time from
mirrored data centers in a global computer network.mirrored data centers in a global computer network.
Utility # 20020124080Utility # 20020124080
• Method for generating a network map. Utility #Method for generating a network map. Utility #
2002007823720020078237
• Method and system for protecting websites fromMethod and system for protecting websites from
public Internet threats. Filed 15 July 2002public Internet threats. Filed 15 July 2002
36. PrinciplesPrinciples
• Open design principleOpen design principle
- You need all the help you can getYou need all the help you can get
- Do not eliminate the obvious without trying firstDo not eliminate the obvious without trying first
- Give serendipity a chanceGive serendipity a chance
• Scaling principleScaling principle
- factor 10 difference means different domainfactor 10 difference means different domain
- different domains need different techniquesdifferent domains need different techniques
• The common case principleThe common case principle
- Zipf law is your friendZipf law is your friend
- things clusterthings cluster
- optimize the common caseoptimize the common case
37. ConclusionConclusion
• The Internet will never be fast enough in allThe Internet will never be fast enough in all
placesplaces
• People will want access to the Internet allPeople will want access to the Internet all
the time and everywherethe time and everywhere
Editor's Notes
Mention that in a nut-shell this is the problem you tried to solve and here you will talk about the ideas that go into the solution
Talk about how DNS cloud works in a bit—like 411 service.
Mention that the bulk of the time is spent in the web transfer and DNS is typically 20 to 50ms whereas the web transfer can take 2 to 5s
Trying to get IP address for www.xyz.com. First go to internic to get xyz.com address.
Explain caching with TTLs. Many people share local nameserver.
Same as before but most content is local! Transparent to end-user.
Very simple process.
Network congestion is reduced because traffic is moved to the edge
Scalability is improved because with more servers more requests can be served
Fault-tolerance improved because no single point of failure - distributed system
Vulnerability reduced because denial of service attacks are diffused
Reduced costs because of economies of scale, multiplexing and buying in bulk
Say high end traffic management system for mirrored websites
Sufficient to have mirrored websites, do not need to use content delivery
Under security mention SSL certificates
If nobody asks why not use DNS queries then bring it up by myself - point out that 15 - 20% of nameservers are closed to the world, that their state tends to be variable, different size packets cannot be used and sysadmins tend to be sensitive about repeated queries.
Talk about as a naive attempt to do the impossible. Experts said it was not possible but say that we learnt important things. Never eliminate the obvious without trying it. Also known as the open design principle - need all the help we can get.
Scalability is the key problem. Say that 10s was set as a challenge
Mention that the naive approach taught us a lot. To some extent we were theoreticians and by doing we learnt.
State that fewer than 1% or 5,000 require proxy pairs.
Talk about war story of how even though our boxes were in same data center as Y! nevertheless we saw different connectivity.
Talk about dos failover
Mention Jerry Saltzer's design principles
Say patents can be gotten from www.uspto.gov
Say that you are stepping back
Mention Jerry Saltzer's design principles
Talk about e2e principle and forethought on original designers. Talk about ubiquity access where people are and info about where they are not - sensor networks, mobility.