sql server scale out with DPV

See more:

SQL-Server

scalability

Hi.
Our company manages an online auction and shopping website(something like ebay), and I have questions regarding to scaling out solutions.

we are running Sql Server 2008 R2 Enterprise edition(which is servicing asp.net) on our two servers which are near each other.
server specifications:

Server 1:
4 x Intel Xeon E5-4650 CPU Processor 8-Core 2.7GHz/20MB/8GT
14 x Samsung 16GB DDR3-1600

Server 2:
4 x Intel Xeon E5-2670 CPU Processor 8-Core 2.6GHz/20MB/8GT (1 per each Node)
4 x Samsung 16GB DDR3-1600

currently we have a 2G Database!


I know it is not considered as a large-scale website but since we are expecting gradual growth I am searching through scaling out solutions.
From what I have read so far it seems "distributed partitioned views" can work fine among things like scalable shared database, p2p replication, DDR,... because we are not willing to make major changes in application,and we have frequent updates(users insert new items to sell,...).
although i do have some concerns relating to performance of linked servers. since servers are near each other I thought maybe a physical solution (LAN) would be more appropriate in connecting the two.
another thing is about restrictions of a view in order to be updatable (like not having any identity column in base tables) and the fact that I think using "instead of triggers" can slow the performance.

am I right in choosing "DPV"?

I appreciate any help, and thank you for your time.