Raid 1 or Raid 1+0 for SQL Server Architecture We are looking at new servers.  Today our SQL Servers are built as follows: 


C/D on RAID 1 , 
E : Tempdb on RAID 1, 
F:log files on RAID 1 , 
G : Catalog data on RAID 1 , 
H: model data on RAID 1 , 
I : symbols on RAID 1, 
J: DB maintenance on RAID 1 , 


So we have a lot of SSD’s, all on RAID 1 with no sharing. 

We are considering changing to a large RAID 1+0.  However the concern is if we will end up with performance impacts since there are random reads that happen throughout the day but not as much as writes.

My question is - whether a large 1+0 RAID is suggested / recommended, which would reduce the quantity of SSD’s that we use and allow us to expand a single container easier or stick with single RAID 1’s?
RAID level 10(1+0) has been recommended by microsoft for high reads. Refer the doc: https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms190764%28v%3dsql.105%29

This level is also known as mirroring with striping. RAID 10 uses a striped array of disks that are then mirrored to another identical set of striped disks. For example, a striped array can be created by using five disks. The striped array of disks is then mirrored using another set of five striped disks. RAID 10 provides the performance benefits of disk striping with the disk redundancy of mirroring. RAID 10 provides the highest read-and-write performance of any one of the other RAID levels, but at the expense of using two times as many disks.

RAID levels higher than 10 (1 + 0) may offer additional fault tolerance or performance enhancements. These levels generally are proprietary systems. For more information about these types of RAID systems, contact the hardware vendor.