Avoid premature Database Sharding

Someone asked a question on Twitter and I thought it's interesting to answer it here in the show.

I have a 2 million row table used in my CRUD python app, I’m worried that as the table grows my inserts will slow down, should I consider sharding my database or partition the table? thank you

* inserts are fast, queries are slow 0:00
* inserts can be slow 3:00
* indexes/stored procedures
* selects, updates and deletes can be slow 12:00
* add proper indexes.
* simplicity wins, premature optimization is bad 15:20
* crazy things that people say as microservices day 1 scares me


🎙️Listen to the Backend Engineering Podcast
https://husseinnasser.com/podcast

🏭 Backend Engineering Videos
https://backend.husseinnasser.com

💾 Database Engineering Videos
   • Database Engineering  

🏰 Load Balancing and Proxies Videos
   • Proxies  

🏛️ Software Archtiecture Videos
   • Software Architecture  

📩 Messaging Systems
   • Message Queues & PubSub Systems  

Become a Member
   / @hnasr  

Support me on PayPal
https://bit.ly/33ENps4


Stay Awesome,
Hussein