How AppDynamics saved Garmin’s
Christmas
Bertrand Tignon
Internet Applications Manager | Garmin
• Over a decade in the software development industry
• Currently Internet Applications Manager @ Garmin
Java Web Services PaaS
Big Data
CI/CD
No SQL
Canary Releases
Fail Fast
Performance Monitoring
Capacity Planning
Agile
@bertrandtignon
We just sell those GPS
automotive devices, right?
~ 7,000 products
Automotive
Aviation
Marine
Sports & Recreation
Health & Wellness
Vertical Integration15,000 associates
world wide
Each month:
25 million visits to garmin.com
16,000 TB Downloads
60 million
registered customers
An experience beyond
best-in-class devices.
More Data
Better Tools
Tighter monitoring
Drive
Improved stability
Improved performance
Improved impact understanding
‘Make systems resilient and
enable them to self-adapt to incidents.
Monitor and report
on business services.’
https://blog.appdynamics.com/apm/deploying-apm-in-the-enterprise-part-2-apm-maturity-as-youve-probably-never-seen-it-before/
Jim Hirschauer
Refactoring software
- Microservices/Cloud Native
- Deployed on multiple data centers
- Deployed on a PaaS
+
Automations
Allow
Resiliency and Scalability
Primarily for developers
Across multiple data centers
For ~1,000 servers
And hundreds of business transactions
Troubleshooting incidents
Monitoring Rabbit Messaging Queues
JVM Health and Metrics
DB Reliance and metrics
Code performance Analysis
Configuration problems
8 app servers
~200 web services
36 app servers
~650 web services
0
5,000,000
10,000,000
15,000,000
20,000,000
25,000,000
30,000,000
35,000,000
40,000,000
12 times more daily transactions
4 times more servers
3 times more web services
Fitness Wearables
Introduction
• March 26th, 2015
• March 29th, 2015
• April 7th, 2015
• July 18th, 2015 One too many….
Many customers give Garmin devices for Christmas.
Increase of traffic to Support site (Manuals, FAQs)
Increase of device registrations
Increase of Garmin account creations
Increase of logins to applications (Express, Connect, My, etc)
We not only sell devices but an experience. The first one is critical!
Incidents caused by the database being overwhelmed.
Customer
16%
Device
11%
eCommerce
3%
Map
9%
Other
0%
Product
42%
Software
Update
16%
Support
0%
Utilities
3%
• Daily traffic between 80K to
180K per minute
• Incident occurred when traffic
reached 200K per minute
• Traffic per Business Transaction
Business Transactions
Calls per
minute to
the DB
Percentage
Map 70,882 60%
Customer 28,682 24%
Account Management 4,272 4%
Map Update 3,774 3%
Others 3,468 3%
Mobile Device 2,031 2%
Customer Device 1,900 2%
Map Activation 1,416 1%
Storefront 761 1%
Tracking 829 1%
Sign In 771 1%
Customer
16%
Device
11%
eCommer
ce
3%
Other
0%
Product
42%
Software
Update
16%
Support
0%
Utilities
3%
June July Aug Sept Oct Nov
tionses transacweb servic
sransactiondatabase t
relianceDB
Increase database capacity
(from 200K calls to over 300K)
Reduce database reliance
(from 5 to 2.5)
• Increased by 5x Database capacity
• Decreased by 90% Reliance on
Database
It would require a 30x increase of
database utilization to reach new
capacity.
2X increase of traffic to garmin.com
FAQs, manuals, applications, map updates, etc
Over 320,000 device registrations
8x increase
60% increase of logins to applications
Over 130,000 Garmin account creations
6x increase
Please give us your feedback—Session B28330
• Complete the online survey you'll receive via
email later today or via text at:
Text this number: 878787
Text this word: APPSPHERE
• Every time you submit a session survey, your
name will be entered in a random drawing.
We're giving away Amazon Echos
to 5 lucky winners!
• Thank you for your input
APPDYNAMICS CONFIDENTIAL AND PROPRIETARY 28
Win!
Thank you

How AppDynamics Saved Garmin's Christmas! - AppSphere16

  • 1.
    How AppDynamics savedGarmin’s Christmas Bertrand Tignon Internet Applications Manager | Garmin
  • 2.
    • Over adecade in the software development industry • Currently Internet Applications Manager @ Garmin Java Web Services PaaS Big Data CI/CD No SQL Canary Releases Fail Fast Performance Monitoring Capacity Planning Agile @bertrandtignon
  • 3.
    We just sellthose GPS automotive devices, right?
  • 4.
    ~ 7,000 products Automotive Aviation Marine Sports& Recreation Health & Wellness Vertical Integration15,000 associates world wide
  • 5.
    Each month: 25 millionvisits to garmin.com 16,000 TB Downloads 60 million registered customers An experience beyond best-in-class devices.
  • 7.
    More Data Better Tools Tightermonitoring Drive Improved stability Improved performance Improved impact understanding
  • 8.
    ‘Make systems resilientand enable them to self-adapt to incidents. Monitor and report on business services.’
  • 9.
    https://blog.appdynamics.com/apm/deploying-apm-in-the-enterprise-part-2-apm-maturity-as-youve-probably-never-seen-it-before/ Jim Hirschauer Refactoring software -Microservices/Cloud Native - Deployed on multiple data centers - Deployed on a PaaS + Automations Allow Resiliency and Scalability
  • 10.
    Primarily for developers Acrossmultiple data centers For ~1,000 servers And hundreds of business transactions
  • 11.
    Troubleshooting incidents Monitoring RabbitMessaging Queues JVM Health and Metrics DB Reliance and metrics Code performance Analysis Configuration problems
  • 13.
    8 app servers ~200web services 36 app servers ~650 web services 0 5,000,000 10,000,000 15,000,000 20,000,000 25,000,000 30,000,000 35,000,000 40,000,000 12 times more daily transactions 4 times more servers 3 times more web services Fitness Wearables Introduction
  • 14.
    • March 26th,2015 • March 29th, 2015 • April 7th, 2015 • July 18th, 2015 One too many….
  • 15.
    Many customers giveGarmin devices for Christmas. Increase of traffic to Support site (Manuals, FAQs) Increase of device registrations Increase of Garmin account creations Increase of logins to applications (Express, Connect, My, etc) We not only sell devices but an experience. The first one is critical!
  • 16.
    Incidents caused bythe database being overwhelmed.
  • 17.
  • 20.
    • Daily trafficbetween 80K to 180K per minute • Incident occurred when traffic reached 200K per minute
  • 23.
    • Traffic perBusiness Transaction Business Transactions Calls per minute to the DB Percentage Map 70,882 60% Customer 28,682 24% Account Management 4,272 4% Map Update 3,774 3% Others 3,468 3% Mobile Device 2,031 2% Customer Device 1,900 2% Map Activation 1,416 1% Storefront 761 1% Tracking 829 1% Sign In 771 1% Customer 16% Device 11% eCommer ce 3% Other 0% Product 42% Software Update 16% Support 0% Utilities 3%
  • 24.
    June July AugSept Oct Nov tionses transacweb servic sransactiondatabase t relianceDB Increase database capacity (from 200K calls to over 300K) Reduce database reliance (from 5 to 2.5)
  • 25.
    • Increased by5x Database capacity • Decreased by 90% Reliance on Database It would require a 30x increase of database utilization to reach new capacity.
  • 26.
    2X increase oftraffic to garmin.com FAQs, manuals, applications, map updates, etc Over 320,000 device registrations 8x increase 60% increase of logins to applications Over 130,000 Garmin account creations 6x increase
  • 27.
    Please give usyour feedback—Session B28330 • Complete the online survey you'll receive via email later today or via text at: Text this number: 878787 Text this word: APPSPHERE • Every time you submit a session survey, your name will be entered in a random drawing. We're giving away Amazon Echos to 5 lucky winners! • Thank you for your input APPDYNAMICS CONFIDENTIAL AND PROPRIETARY 28 Win!
  • 28.