3 ms·
I've come to appreciate simple APIs like the one exposed by Redis. Such simple APIs tend to require more careful planning to use but they help you to avoid runn
by jongjong 3y ago
I've come to appreciate simple APIs like the one exposed by Redis. Such simple APIs tend to require more careful planning to use but they help you to avoid running operations which are complex and inefficient. They often force you to think about your app architecture in a broader sense in order to solve problems using simpler primitives.
That said, I think the fact that Redis stores everything in memory can make it unsuitable for certain projects as a database where only a small fraction of the whole data set is ever exposed to users at any given time.
- trollied 3y agoI appreciate simple APIs that can be used cross-platform, like SQL.
- cratermoon 3y ago> simple APIs ... SQL Which do you prefer, simple APIs, or SQL?
- deepsun 3y agoThe biggest problem with SQL is that it was designed for humans, for writing by hand, not for programmatic access. So it suffers the same problems as shell commands do.
- ghayes 3y agoI also love thinking through how to store data, e.g. in Redis, and aligning it with your access patterns. The biggest challenge I’ve faced is that access patterns tend to change over time and Redis isn’t flexible (e.g. you use an HSET to pull user data but now you want to query by a different key). So you probably will end up storing data in SQL for persistence and Redis for caching, anyway.