Scalable shared databases VS Active secondary replicas

Hi-

I'm trying to wrap my head around the differences between scalable shared databases vs Active secondary replicas in SQL 2012. Can anyone point out the pros vs cons for each of these solutions?

Here is what I'm trying to accomplish. We've a massive database (~ 10 TB page compressed) and we'd like this data to be available for multiple instances without duplicating this data. Scalable shared databases is one solution, but I see all the literature for SQL2012 pushing towards Active secondaries and I'm not sure about the differences between them.

Also, we need to use SIMPLE recovery model for our databases, we cannot afford FULL recovery mode. What are my options?

Thanks,
Saptagiri