Re:Show HN: Kardinal–The lightest-weight Kubernetes dev envi...
by galenmarchetti on Thursday August 15, 2024 @02:28PM
(#41258993)
service B doesn't actually know that - it happens at the level of the service mesh (you have to have a service mesh installed, right now just supporting istio but we plan on making that configurable)
we use trace headers to keep track of where the request originally came from to route it to the right database. it's transparent to service B as long as service B is properly propagating the request context from incoming request to outgoing requests
Re:Show HN: Kardinal–The lightest-weight Kubernetes dev envi...
by from-nibly on Sunday August 18, 2024 @11:28AM
(#41282937)
Is that at the TCP level or the http level?
How do you handle requests going from service A to B and then to database C vs A2 -> B -> C2?. How does service B know to route to a different database based on the version of A thats different?