Hacker News new | ask | show | jobs
by pkulak 3891 days ago
If you start doing this, think long and hard about your architecture choices.
2 comments

This is such a banal and not-constructive comment. Of course he would think about architectural choices. Your comment suggests one of the following:

1. The proposed feature is harder than other proposed features (which ones and why? edit: it turns out there isn't even a proposed feature here...)

2. You see pitfalls or good choices and bad choices (which ones and why?)

Either way, your comment as it stands isn't helpful in the slightest, and I'm calling shenanigans. If you are in either camp 1 or camp 2, why not actually say something useful instead of speaking from this glass pedestal of falsified authority.

edit: formatting.

you are aware, by the way, that the antirez' blog post does not discuss (as far as i can tell) implementation of a new feature, but instead just explains a few community best practices that have coalesced over time regarding implementation of multiple indices using one of the redis data structures (zsets)?

but even if he were, what risk would this simple feature pose to the redis architecture such that "long and hard" thought is required to avoid some apparently grim consequence?