Today, Kubernetes is the defacto standard if you want to run container workloads in a production environment, though that wasnt always the case. We had/have a fair amount of monolithic code for our products & to make sure we could build GoCenter in a way that would be easier to manage at the scale we needed to make changes. For us, that meant changes to the way we write code (more Go), how we build apps (using Docker & Kubernetes), & how we deploy (using Helm). We had to figure out a whole bunch of things as we looked at building proper microservices that we could deploy to Kubernetes. During the session, we will pay special attention to things like logging, persistence, limits, & probes because containerizing an app is not simply putting your existing app into a docker container. As were looking at containers, knowing exactly what is in the container in terms of licenses, packages, & vulnerabilities was, & is, incredibly important to us to keep our cluster & data secure.
Throughout the session, well cover the lessons that we have learned building these products, so it will not be a product pitch.
Baruch SadogurskyHead of Developer Relations @jfrog
Baruch Sadogursky (a.k.a JBaruch) is the Head of Developer Relations & a Developer Advocate at JFrog. His passion is speaking about technology. Well, speaking in general, but doing it about technology makes him look smart, & 17 years of hi-tech experience sure helps. When hes not on stage (or on a plane to get there), he learns about technology, people & how they work, or more precisely, dont work together.
He is a CNCF ambassador, Developer Champion, & a professional conference speaker on DevOps, DevSecOps & Development topics, & is a regular at the industrys most prestigious events including DockerCon, Devoxx, DevOps Days, OSCON, Qcon, JavaOne & many others. You can see some of his talks at jfrog.com/shownotes