4 ms·
Most data versioning approaches would help bulk consumers of the data, rather than through the API. You could add a separate "changes" feed to help API consume
by webmaven 10y ago
Most data versioning approaches would help bulk consumers of the data, rather than through the API.
You could add a separate "changes" feed to help API consumers, or inline version info to the main API results.
- hbcondo714 10y agoThanks, was thinking about doing a new endpoint for changes too but wanted to see if this topic of data versioning pertains to this or not
- webmaven 10y agoIt does, but I think what you're really after here is a mechanism for cache invalidation. Check out PostgreSQL's LISTEN and NOTIFY: https://www.postgresql.org/docs/9.6/static/sql-listen.html https://www.postgresql.org/docs/9.6/static/sql-listen.html https://www.postgresql.org/docs/9.6/static/sql-notify.html https://www.postgresql.org/docs/9.6/static/sql-notify.html A related HN discussion a few years ago: https://news.ycombinator.com/item?id=6689213 https://news.ycombinator.com/item?id=6689213