There is no silver bullet. Caching is hot and database scaling architecture is very specific to your application. "Feature based partitioning" sounds cool but

There is no silver bullet. Caching is hot and database scaling architecture is very specific to your application. "Feature based partitioning" sounds cool but does the data access layer do the cross database joins?? "Vertical partioning" again the data access layer can get complicated. I wish this was available as a piece of technology or service.