nxnwtech V: Inner Loop Dev on K8s: Local? Cluster? Both!

Title: Inner Loop Development on Kubernetes: Local? Cluster? Both!
Speaker: Florian Moss (Red Hat)

Cloud native technologies also fundamentally altered the developer experience. Not only are engineers now expected to design and build distributed service-based applications, but their entire development loop has been disrupted. No longer can developers rely on monolithic application development best practices, such as checking out the entire codebase and coding locally with a rapid “live-reload” inner developer loop. They now have to manage external dependencies, build containers, and implement orchestration configuration (e.g. Kubernetes YAML).

This may appear trivial at first glance, but this has a large impact on development time.

If a typical developer codes for 360 minutes (6 hours) a day, with a traditional local iterative development loop of 5 minutes -- 3 coding, 1 building i.e. compiling/deploying/reloading, 1 testing inspecting, and 10-20 seconds for committing code -- they can expect to make ~70 iterations of their code per day. Any one of these iterations could be a release candidate.

This talk will look at 3 different options on inner loop development, (1) local, (2) local/remote (Telepresence) and (3) on-cluster development.

-------
Florian is the Hybrid Cloud Practice Lead for Red Hat Ireland, working with clients on implementing cloud-native platforms that allow for faster application delivery, lower failure rate, and less lead time.

Having worked with public and private sector clients on OpenShift implementations, it became clear the developer experience is one of the most important aspects of any Kubernetes/OpenShift rollout.