Certificate: Data: Version: 3 (0x2) Serial Number: 55:7f:b3:00:f8:b2:24:50:dc:51:7c:e5:85:5a:14:7a:65:28:26:38 Signature Algorithm: sha256WithRSAEncryption Issuer: C = US, L = Redmond, O = LearnCloudNative, CN = getistio.learncloudnative.com Validity Not Before: Feb 10 17:24:51 2021 GMT Not After : Feb 10 17:24:51 2022 GMT Subject: C = US, L = Redmond, O = LearnCloudNative, CN = getistio.learncloudnative.com Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) ...
What are sticky sessions and how to configure them with Istio?
The idea behind sticky sessions is to route the requests for a particular session to the same endpoint that served the first request. That way to can associate a service instance with the caller, based on HTTP headers or cookies. You might want to use sticky sessions if your service is doing an expensive operation on first request, but later caching the value. That way, if the same user makes the request, the expensive operation will not be performed and value from the cache will be used.
Sidecar Container Pattern
The sidecar container aims to add or augment an existing container's functionality without changing the container. In comparison to the init container from the previous article, the sidecar container starts and runs simultaneously as your application container. The sidecar is just a second container you have in your container list, and the startup order is not guaranteed.
Branch by Abstraction Pattern
The strangler pattern is useful for scenarios where you can intercept the calls at the edge of your monolithic application. But what do you do in a scenario where the functionality you're trying to extract is not called directly from the outside, rather it is being called from multiple other places inside the monolith?