SpringOne Platform 2019 Fast 5 Things You Can Do Now to Get Ready for the Cloud Speaker: Robert Sirchia, Practice Lead, Magenic Technologies YouTube: https://youtu.be/WLw82cV0Lwk

1. Fast 5 Things You Can Do
Now to Get Ready for the
Cloud
October 7–10, 2019
Austin Convention Center

2. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Introduction

3. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Who am I?
I am a Practice Lead Consultant with Magenic,
heading up the Cloud Practice, and has more than
15 years’ experience with the .NET and Microsoft
technologies. He has been working with the Pivotal
Platform in the .NET space for more than four years,
and during that time, I have led large re-platforming
and modernization efforts in moving .NET
applications to Pivotal Platform.
I also has industry experience in real estate,
financial institutions, politics, and energy and
chemical.

4. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Who I am not
This isn’t me…

5. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Approach

6. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
The 12 factor App*
I. Codebase
II. Dependencies
III. Configuration
IV. Backing Services
V. Build, Release, Run
VI. Process
VII. Port Binding
VIII. Concurrency
IX. Disposability
X. Dev to Prod Parity
XI. Logs
XII. Admin Processes
* https://12factor.net/

7. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Now there are 15…
If you want to know more about the new factors
https://content.pivotal.io/ebooks/beyond-the-12-factor-app
By: @kevinhoffman

8. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Focusing on Five
• Codebase
• Configuration
• Build, Release, Run
• Disposability
• Logs
Fast Five
In no particular order

9. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Codebase
One codebase tracked in revision control, many deploys

10. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• What we did before looked a lot like
this.
• Not always.
• We have been known to have
solution files with over a hundred
project references.
Codebase of the Past
Dev
App
API
Batch

11. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Centralize all ecosystem code in
one code base
• Clean up references
• Circular (very bad)
• One place to…
• Refactor
• Consolidate
• Restructure
• CI/CD is easier
• Share libraries by reference
Codebase Moving Forward
App
API
Batch
App

12. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Branching of the Past
Dev QA Prod
Develop QA Release
Build
Deploy
Changes
Changes
Changes
Changes
Changes

13. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Pick a modern branching strategy that works for you.
• GitFlow
• GitHub Flow
• GitLab Flow
• Git Simple
• Don’t allow long running feature branches
• Push often and use feature flagging as much as
possible to avoid creating branches
Branching Moving Forward

14. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Should look something like this…
Branching Moving Forward
master
develop
feature
feature

15. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Build, Release, Run
Strictly separate build and run stages

16. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Build, Release, Run of the Past
Changes
Release
Prod
Build
Deploy
DLL
Wait our reference to this DLL is
off!!!
We need to change the config!!

17. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Build, Release, Run going Forward
Build process needs to ensure
the correct references are pulled
Wait what about configuration?
Changes
Release
Prod
Build
Deploy
DLL

18. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Don’t do a build per environment (see configuration)
• Deploy many assures that code developers built, QA tested, and stakeholder
signed off on, is the same
• This allows you to roll forward and roll back
• Allow the recapitulation of a deployment for trouble-shooting
• Build once allows compliance teams to track versions customers are using at a
point in time
• The same can be said for InfoSec
Build Once Deploy Many

19. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Configuration
Store config in the environment

20. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
End all and be all is the web or app config
Configuration of Today
Artifact
Develop Build Deploy Dev
Dev
QA
dev
config

21. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
This is fine but…
Configuration of Today
Artifact
Dev
Artifact
Artifact Artifact
Artifact Artifact
Artifact Artifact
Artifact Artifact
DevDevDev Dev
Artifact
Artifact
Artifact
Artifact
Artifact
Artifact
Artifact
Artifact
Artifact
Artifact

22. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Configuration Server
• Centralized configurations
• Served through Config Server
• Stored in Vault, GIT, or local file system
Configuration moving forward

23. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Configuration Server deploys anywhere with
docker or directly to a server.
And can be migrated to the cloud later…
WAIT! I am not in the cloud!

24. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Disposability
Maximize robustness with fast startup and graceful shutdown

25. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Application that start slowly have stability issue in the cloud because their host
may not recognize that the app is healthy and raise a warning or recycle them
• Startup time < 15 seconds, ideally 500 milliseconds or less
• Avoid in memory caching to improve start up time and stability
• Redis or external caches are ideal replacements
When Starting Up

26. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Application that shut down slowly may lose units of work because their process
is terminated before computing completes
• Shut down time < 5 seconds, ideally 250 milliseconds or less
• Shut down process should not result in loss of work
When Shutting Down

27. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Logging
Treat logs as event streams

28. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Logging to the file system
• Logging from multiple locations
• Logging to the Event Viewer
Logging of Today
service
ctrl
service
logger
Log Location
ctrl
logger
service

29. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
• Centralize on single framework:
• log4net
• NLog
• Serilog
• Or platform native logging:
• System.Dianogstics
• Microsoft.Extentions.Logging
• Etc.
• Adjust to have one point that actually
writes to your current logging system
• Make sure logs are flushed aggressively
Logging Frameworks

30. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Additionally, log good things to STDOUT and bad things to STDERR
Logging moving Forward
service
ctrl
service
logger
Log Location
ctrl
logger
service
service
ctrl
service logger Log Location
ctrl
service

31. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
No…
This is a start. We have learned that chaotic logging makes modernization efforts
nearly impossible.
This is by no means a complete logging strategy.
Wait is that it?!

32. Stay Connected.
make us proud be prepared for the cloud
#springone@s1p

33. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Somethings To Take Away
Start somewhere
Five examples of where to start
Small Increments
Document well

34. Thank you
#springone@s1p