There is a slight difference I believe. With the TTL as it’s designed in the lib I wanted to force closing the connection even though we have some traffic. If we setup a Keepalive that is never reached (because we have traffic every second whereas the Keepalive is set to 2 secs for example), the connection will never be closed. So we won’t be able to…
Hi Salmaan. Thanks for your post.
How about elasticity? When we scale up the number of replicas for example. Will the client schedule a call to the headless service to refresh its cache so that it can “discover” the new replica?
Cool post but I’m more in favor of persisting in an event store the resulting change of a command on an aggregate state.
Indeed, the business logic on how to apply a command may change over time. It means rehydrating an aggregate using our event store may result in something different over time.