3 ms·
It looks to me like a bad architected solution... If you have a background job to update data, there is no need to do any TTL. If we're speaking about currency
by pachico 4y ago
It looks to me like a bad architected solution...
If you have a background job to update data, there is no need to do any TTL.
If we're speaking about currency exchange, you might prefer to store a transactional history of exchanges, together with the current one, and populate a fast read model too (Redis) with a failover against the oltp version...
Maybe it's just me.
- kinduff 4y agoI agree with you, it is bad architecture. I didn't mention it in the blog post, but the TTL was introduced by a dependency that allowed us to integrate the rate exchange service.