Adding new microservice in K8S, is easier than ever, but as we all know, with great power comes great responsibility. As the number of microservices increase, the cost of managing them and the dependencies between them also increase exponentially. In this talk I shall provide an end-to-end example on how to build and manage microservices on k8s; and walk you through the following steps:
Understand why Helm, a package manager for k8s, is important; and how to use it properly when handling a large amount of microservices (‘Umbrella chart to the rescue’). Discuss how to build a basic pipeline in Jenkins, suited for the k8s world. Realize how using these tools guarantees your dev team can move faster (and break things) while keeping the business on safe ground.
Microservices are ‘easy’, dependencies are hard: The right way to build a cloud-native CI/CD
A Backend developer/Devops - ever since finishing my CS/Psychology degree.
Started working at eBay but felt it's too big.
Joined a 50 ppl startup (Forter) but it got big again.
So now I'm a first developer (Rookout) - hope to make my company big :)
On the past i worked mainly with distributed systems and big data (Storm/ES etc).
And On my current job I'm responsible for the Infra side - building a full cloud native CI/CD from scratch using the latest technologies, and making sure we have the right logging and monitoring to make sure nothing breaks.
I Really love the k8s ecosystem and try pushing the limits of how fast and safe we can have the R&D moving, While making sure no one live in fear (developers or management) of the system bursting into flame.
Love learning new things, feel like the tech world is HUGE and growing like crazy, And I like being on the cutting edge of it :)