For the particular software (financial suite), it looks like SAS or SSD is the way to go then (did they happen to give you a number for IOPS?).I gave the SW vendor a quick call. The app is truly multi threaded. Multi core CPU, amount of RAM and random read IOPS increase productivity - that's what the guy have said.
I think I'll go with two arrays (will still give some more thought to it):
Two MLC based SATAIII SSDs in RAID0 (for this particular app, highest possible performance, no need for parity)
Remaining six disks (have to think which) in RAID5 (?) for video editing (Premiere / AE).
I believe mixing disks like this in the enclosure wouldn't be a problem.
The other two factors, is capacity and budget to get any further on the specifics.
Also, as per the library, if it doesn't change often (application isn't writing to that particular set), then you could get away with a stripe set if you can afford the time needed to fix it (remember, you'd have to do this manually with RAID 0 = replace disk, then restore the data from a backup). If you can't put in the time, or the application will frequently update the set, then a redundant array is called for (if it's MLC based SSD's, then stick to 1 or 10, for a redundant level). You'll have more options with SAS, as they can take parity based arrays (straight forward or nested variants = 50/60/51/61).
As per the video editing, mechanical SATA is the way to go (assuming this system isn't going to be used as a SAN). RAID 5 gives a nice balance of redundancy, price, and performance, but should only be undertaken if you or someone else you trust will have daily access to the system just in case there's a failure (that way it can be dealt with quickly, particularly if you don't run a Hot Spare).
If it's a remote system, or a qualified person doesn't have access to it on a high enough frequency (i.e. may only have a tech show up when it breaks, and they have to drive in - not something that can be done via a remote access client), then RAID 6 + Hot Spare would be in order.