After 1 year of launch, ride sharing increased a lot resulting in a lot of insertion requests to the database. Consider there is no room to further increase the size of server and changing database is not an option. How would you solve the massive slow in

After 1 year of launch, ride sharing increased a lot resulting in a lot of insertion requests to the database. Consider there is no room to further increase the size of server and changing database is not an option. How would you solve the massive slow insertion of each ride request? 

*NO IMPLEMENTATION REQUIRED IN THIS QUESTION.