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.
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
Cloud Foundry Summit 2015: Leaving your Comfort Zone - Garmin and Cloud Foundry
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
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
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