Cloud computing environments have been designed around the needs of web development companies with in-house software development teams. Devops engineers write software specifically around the capabilities of their cloud provider, making full use of the elasticity and flexibility these environments provide. Much of the software our higher education enterprises depend on assumes a more static and unchanging platformsthan the cloud provides. How then do we bring legacy macroservices into these highly dynamic environments?
This talk focuses on how UCSC has refocused its Systems Engineering teams away from delivering individual servers, and towards building infrastructure code that reliably produces flexible, secure and stable cloud platform environments. If building and delivering a set of servers is “pounding a nail”, delivering a set of well-tested and consistent infrastructure templates and configuration management code is “building a hammer”. We are now in the business of forging hammers.
]Much of this talk will, by necessity be specific to AWS, but conceptually it can be easily applied to any cloud service provider.
Basic conceptual knowledge of cloud architecture.