How to scale writings in your DB without recurring to sharding?

The complexities in the code can be avoided by using transparent sharding tools, which ease all the heavy lifting associated with sharding. Check out ScaleBase for more info.

Nice tech, thanks +1 – SDReyes Jun 15 at 18:13.

Normally ... avoid indexes and foreign keys in big tables. Every insert/update on a indexed column implies rebuilding partially the index and sometimes this can be very costly. Of course, you'll have to trade query speed VS writing speed but this is a known issue in database design.

You can combine this with a NoSQL database with a some sort of mechanism for caching queries. Maybe a fast NoSQL system sitting in front of your transactional system. Another option is to use transactions in order to do many writes in one go, when you commit the transaction the indexes will be rebuilt but just once per transaction not one per write.

– SDReyes Jun 3 at 22:11 Yes, I meant that. There was a typo. – msalvadores Jun 3 at 23:41.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.