While the scenario described by Ben O’Steele’s ☞ article — using Redis for log based analytics — might not be interesting to everyone , it made me think once again about the importance of data modeling in the NoSQL space.
With all the fun and excitement around NoSQL, it’s easy (maybe too easy?) to stuff your data in your preferred NoSQL solution due to its simplicity and speed. But, you should step back and think about:
- how to model your data
- what data access patterns will your application need
- how you deal with data integrity/consistency (what happens if two applications will need to access the same data in read/write mode?)
- what is the final complexity, performance, scalability of the solution based on the decisions you’ve made to the above points.
It is only then that you should start saving your data!