Getting Started with Istio and Minikube
Istio is the new standard for microservices in Kubernetes. Around 2014 Netflix defined before everybody else how to do proper microservices using they brand new stack called NetflixOSS. Introducing game-changing concepts for the Cloud Native microservice components such as Mid-tier load balancing, fault tolerance, circuit breaking, retry/timeouts, service registry and discoverability and much more. NetflixOSS was super important and still is in the cloud-native microservices world. Today the great majority of companies who do Java development use
NetflixOSS Stack directly or via Spring Cloud Abstractions. IMHO the main benefit Spring Cloud added was documentation. Today several NetflixOSS components are deprecated or like how Netflix like to call it MANTAINCE_MODE you can check that in any NetflixOSS project on Github by looking the file OSSMETADATA. As you can see here Hystrix is in mantaince mode. One of the reasons is because there is a better way to deal with the problem, for Hystrix there are adaptive thresholds but also because the world is changing fast. Today in 2019 Kubernetes makes more sense them ever as becoming the true multi-poly cloud solution. Kubernetes with Istio(using Envoy) fix some of the problems of the NetflixOSS Stack such as being binary coupled and very hard to work without java. Today I will show a quick DEMO on how to run istio in Minikube(local env) and also a quick presentation on some k8s and istio concepts. Hoje you All enjoy.
Why Istio?
Basically, all that the NetflixOSS stack for microservices was doing was moved to the platform and outside of your classpath. So this means Kubernetes, Istio, and Envoy are doing all the heavy lifting for you. Also, you still have the same cloud-native game-changing capabilities but now you are free to use any language, any server, any architecture as long and you pack your image with Docker. This pattern introduces greater flexibility to the developer and you still benefit from kubernetes abstractions meaning your code easily run multi-cloud.
Istio Slide Deck
ThatÅ› it guys. I will be posting more about Kubernetes and Istio soon. I hope you enjoy and take care.
cheers,
Diego Pacheco
NetflixOSS Stack directly or via Spring Cloud Abstractions. IMHO the main benefit Spring Cloud added was documentation. Today several NetflixOSS components are deprecated or like how Netflix like to call it MANTAINCE_MODE you can check that in any NetflixOSS project on Github by looking the file OSSMETADATA. As you can see here Hystrix is in mantaince mode. One of the reasons is because there is a better way to deal with the problem, for Hystrix there are adaptive thresholds but also because the world is changing fast. Today in 2019 Kubernetes makes more sense them ever as becoming the true multi-poly cloud solution. Kubernetes with Istio(using Envoy) fix some of the problems of the NetflixOSS Stack such as being binary coupled and very hard to work without java. Today I will show a quick DEMO on how to run istio in Minikube(local env) and also a quick presentation on some k8s and istio concepts. Hoje you All enjoy.
Why Istio?
Basically, all that the NetflixOSS stack for microservices was doing was moved to the platform and outside of your classpath. So this means Kubernetes, Istio, and Envoy are doing all the heavy lifting for you. Also, you still have the same cloud-native game-changing capabilities but now you are free to use any language, any server, any architecture as long and you pack your image with Docker. This pattern introduces greater flexibility to the developer and you still benefit from kubernetes abstractions meaning your code easily run multi-cloud.
Istio Slide Deck
Istio from Diego Pacheco
Istio Video presentation + DEMO
Installing Istio on Minikube(gist)
Installing Istio on Minikube(gist)
ThatÅ› it guys. I will be posting more about Kubernetes and Istio soon. I hope you enjoy and take care.
cheers,
Diego Pacheco