SpingOne Platform 2016 Speaker: Philip Glebow; Director IT, Gap The Gap is rapidly adopting Cloud Foundry. As part of that adoption, our developers are adapting to a new set of patterns, tools and processes. This talk focuses on what patterns worked for us in considering integration, messaging, data, scaling, and other concerns. We’ll share what we've learned, how we’re rapidly delivering new capabilities with Cloud Foundry and where we’re headed next.

1. Gap Inc.’s Cloud
Migration:
Lessons Learned

2. Philip GlebowDirector
Architecture
Gap Inc.

3. Introduction
• This talk covers some of the lessons learned during
our initial adoption of PCF at Gap Inc.
– Patterns
– Tools
– Techniques

4. Road Map
• Patterns, Tools, Techniques
• Challenges
• Next Steps
• Q & A

5. µ Services, Rapidly Deployed

6. RabbitMQ
• Rapidly deployed Rabbit
MQ (OpenStack)
• Use case: Changes to the
in-store date automatically
cause the allocation of
inventory to update in
near real-time
• Parallelism when building
services

7. Data
• Challenging
• Gap Inc. has decades of
legacy systems & data
centers
• Spatial locality of
services + data matters
• Data Virtualization

8. Auto-scaling
• RabbitMQ allows us to
horizontally scale
• When the CPU utilization
spikes, PCF automatically
adds new workers to
meet the demand
• Reactive scaling vs.
predictive scaling

9. Application Performance Monitoring
• We actively monitor
performance with
APM tools
• PCF doesn’t offer
much here
• Developers are able to
identify, diagnose and
solve performance
issues quickly

10. Logging & Splunk
• Splunk is widely used to
capture & report
application state
• All logging from PCF goes
into Splunk
• Dashboard per app
• Alerts when errors are
detected
• Some overlap with APM

11. Challenges

12. Challenges - Spring Cloud Config
• Hand encryption, no key rotation, Git with secrets
• Git is a single point of failure
• Complexity with web hooks during B/G deploy
• The audit trail in Git does not indicate when a change
was present in production, only when it was
committed to the repositorry
• Pivotal said “Let’s fix this together”

13. Spring Cloud: Vault + Consul
• Joint development by
Gap Inc. & Pivotal
• Spring Cloud Config polls
Consul for changes
• More details at the
presentation by Nivesh
Gopathi (11:45 AM,
Bristlecone 4)

14. Challenges – Data Services
• Testing Tesora
(DBaaS)
• PCF 1.8 will improve
support
• How do we make
experience seamless
when we move to
public cloud?

15. Challenges - IPsec
• Gap Inc. has very strong
security requirements
for PII
• IPsec add-on used to
secure data in transit
within PCF

16. Next Steps: Migration to Public Cloud
• Public cloud gives us
Speed & Scale
• New technologies
• Geographic proximity
• Some Concerns

17. Q & A

18. Biography of the Presenter
Philip Glebow is a software architect at Gap Inc. Inc. and is the product
architect for pricing in the planning domain. Prior to joining Gap Inc.
Inc., Mr. Glebow worked as a software architect in financial services for
Blackrock, Inc. and Barclays. He began his career as a consultant where
he worked on complex custom software solutions in the Information,
Communications and Entertainment practice at BearingPoint
(previously KPMG Consulting, Inc.). Mr. Glebow holds a Bachelor of
Science in Computer Engineering from Cal Poly San Luis Obispo and a
Masters of Science in Bioinformatics from the Johns Hopkins
University. He may be reached via LinkedIn at
www.linkedin.com/in/philipglebow or at pglebow@gmail.com

19. References
• Spring Boot - http://projects.spring.io/spring-boot
• Cloud Foundry - https://www.cloudfoundry.org
• The Twelve-Factor App - http://12factor.net
• Rabbit MQ - https://www.rabbitmq.com
• MongoDB - https://www.mongodb.org