This document discusses Garmin's transition from an on-premise infrastructure to a cloud-based platform hosted on Pivotal Cloud Foundry. It highlights issues with the previous environment such as workload of maintaining infrastructure, suboptimal resource utilization, and roadblocks to developer productivity. The new platform automates infrastructure deployment, provides self-healing and auto-scaling capabilities, and allows developers to focus on business needs through continuous deployment. Key aspects of the new architecture include load balancing, availability zones, centralized monitoring with tools like vRealize Operations Manager, and application monitoring with AppDynamics.

1. Leaving Our Comfort Zone
Alex Curtis (Production Management)
Brandon Henry (Operations)
Bobby Hubbard (Architect)
Jonathan Regehr (Developer)

2. Who we are
• Based in Olathe, Kansas
• Founded in 1989
• Revenue of $2.9 billion (2014)
• Markets include Marine, Outdoor, Fitness, Aviation & Automotive/Mobile

3. The Past

4. The Past

5. The Present

6. The Present

7. Stay Connected with Connect

8. Stay Connected with Connect

9. Single Sign On

10. Why Change?
• Infrastructure Build-­out Workload
• Suboptimal Infrastructure Utilization
• Labor-­intensive Monitoring & Security
• Hard-­to-­reach Uptime Goals

11. Why Change?
• Roadblocks to Developer Productivity
• Response Time to Business Needs
• Improve Project Costs

12. Why Change?
“Sample” Application Outage
Could happen at any time
Impact
• Customer-­facing App running slow
• Some Users Unable to Log in
Cause: Heavy load brought down a critical supporting app
Solution: Double app server pool size

13. Why Change?
Monolith App Server Farm
“We take the whole football team to kicking practice”
Current State
• Large App Server Pool
• Multiple WARs per server
Need: higher capacity for One App
Solution: Scale the entire app suite as a unit

14. How Did We Get Here?
Garmin Hackathon
Pivotal Cloud Platform Roadshows
Proof Of Concept

15. POC: Datastores
User-­provided
Single vs. Multiple
Non-­JDBC

16. If you build it …

17. Well actually …

19. • Cloud Services
• Actuator -­ health++
• Cloud Connectors

20. • Eureka
• Hystrix
• Feign

21. Why Change
• Infrastructure Build-­out Workload
• Automated infrastructure deployment
• Suboptimal Infrastructure Utilization
• High application to Infrastructure ratio
• Labor-­intensive Monitoring & Security
• Automated monitoring & Updates
• Centralized security updates
• Hard-­to-­reach Uptime Goals
• Self-­healing platform
• Automated load-­based scaling

22. PaaS: Problem Resolution
• Roadblocks to Developer Productivity
• Push-­button deployments
• Developers focused on business requirements, not
environment build-­out
• Response Time to Business Needs
• Agility Through Continuous Deployment
• Improve Project Costs
• Push-­button project infrastructure build-­out
• CI/CD yields faster feedback cycle

23. Why Change? Outage Prevention.
Auto-­Scaling
Sometime in the near future
Impact: Imperceptible App Slowdowns
Cause: Heavier-­than-­normal service traffic
Solution: Scale up

24. Why Change? Scalability.
CloudFoundry-­Managed Apps
“Kickers get their own practice field”
Future State
• Instances grow and shrink as necessary
• Apps securely nestled in their containers
Need: higher capacity for One App
Solution: Let CloudFoundry scale the app as needed

25. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

26. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

27. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

28. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

29. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

30. NGINX

31. NGINX
Legacy, context-­based
URLs and addresses
Example:
sso.garmin.com/auth
Cloud Foundry-­friendly
application URLs and
addresses
Example:
sso.cf.garmin.com/auth

32. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

33. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

34. Routers
Droplet
Execution
Agents
Architecture Overview

35. Architecture Overview
Routers
Droplet
Execution
Agents
Routers
Droplet
Execution
Agents
Routers
Droplet
Execution
Agents
Availability Zone 1
Availability Zone 2

36. Architecture Overview
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com
app.garmin.com

37. Architecture Overview -­ Future
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com

38. Architecture Overview -­ Future
APP.GARMIN.COM
app.kcg-­
cloud.garmin.com
app.ola-­
cloud.garmin.com

39. Architecture Overview

40. CF Operations Manager

41. CF Operations Manager

42. CF Operations Manager

43. CF Operations Manager

44. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

45. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

46. CF Operations Manager

47. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

48. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

49. Monitoring -­ SolarWinds

50. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

51. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

52. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

53. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

54. Monitoring
vRealize Operations Manager
vRealize Hyperic
Pivotal CF Ops Metrics

55. Monitoring – vRealize Operations Manager
vRealize Operations Manager

56. Monitoring – vRealize Operations Manager
vRealize Operations Manager

57. Monitoring – vRealize Operations Manager
vRealize Operations Manager

58. Monitoring – vRealize Operations Manager
http://blog.pivotal.io/cloud-­foundry-­pivotal/products/monitoring-­
pivotal-­cloud-­foundry-­health-­and-­status-­hybrid-­models-­kpis-­and-­
more

59. 100% Uptime
Routers
DEAs
Apps

60. 100% Uptime
Routers
DEAs
Apps
Health Monitor

61. 100% Uptime
Routers
DEAs
Apps
Health Monitor

62. 100% Uptime
Routers
DEAs
Apps
Health Monitor vRealize Ops Manager

63. 100% Uptime
Routers
DEAs
Apps
Health Monitor vRealize Ops Manager

64. Application monitoring

65. Application Monitoring – AppDynamics
Environment
(Application)
Cluster
(Tier name)
Server
Layout (pre-­CF)

66. Application Monitoring – AppDynamics
New Build PackOriginal Build Pack

67. Application Monitoring -­ Splunk

68. Application Monitoring -­ Splunk

69. Production Management

70. Summary
• Infrastructure Build-­out Workload
• Suboptimal Infrastructure Utilization
• Roadblocks to Developer Productivity
• Labor-­intensive Monitoring & Security
• Hard-­to-­reach Uptime Goals
• Response Time to Business Needs
• Improve Project Costs

71. Summary

72. Questions?