SQL Server only supports active-passive clustering. It does not offer anything that is comparable to Oracle RAC or IBM PureScale. Therefore it is not possible to have several active database instances.
For query type applications it is possible to clone the same database several times. For update-type workloads it might be possible to partition the data set and allow only one active node to update the corresponding "partition" of data. Partition as described in the last sentence has nothing to do with the partitioning functionality it describes node-ownership of data.
But generally if such a requirement needs to be supported it is better to switch to a product that supports the functionality (like Oracle RAC). The above solutions simply do not scale well in terms of development time and manageability.