First of all, 50GB per day is easy. Now, maybe contrary to what they say below, do the following:<p>* Don&#x27;t use queues. Use logs, such as Apache Kafka for example. It is unlikely to lose any data, and in case of some failure, the log with transactions is still there for some time. Also Kafka guarantees order of messages, which might be important (or not).<p>* Understand what is the nature of data and what are the queries that are made later. This is crucial for properly modeling the storage system.<p>* Be careful with the noSQL cool-aid. If mature databases, such as postgreSQL can&#x27;t handle the load, choose some NoSQL, but be careful. I would suggest HBase, but your mileage may vary.<p>* NoSQL DBs typically limits queries that you might issue, so the modelling part is very important.<p>* Don&#x27;t index data that you don&#x27;t need to query later.<p>* If your schema is relational, consider de-normalization steps. Sometimes it is better to replicate some data, than to keep relational schema and make huge joins across tables.<p>* Don&#x27;t use MongoDB<p>I hope it helps!