architecture - How far can one take SimpleDB, OpenID and the Cloud? -

I have ASP.NET MVC app (non-functional, social) Working on I work on .NET authorization The provider started to use, but the day I was thinking in the cloud lining was becoming more shining

Eventually I want to run away with the host to host the SQL Server database by ISP and to start using S3 slowly as my content increases.

I am considering using Authentication and OpenID for SimpleDB to store user details. If I understand correctly, any content added by the user can be key to the claimant.

What are the advantages / disadvantages of doing this? What are the showstoppers of this approach?

Does anyone have any examples of pure cloud architecture that can be used to support arguments against / against?

I think the benefits of using open-ended are quite well known. Benefits of using SimpleDib to store user details include:

• Flexible schema allows you to support certain types of dynamic user data directly in a RDBMS Can be cumbersome with For example, users define profile profiles, or email addresses such as arbitrarily long lists. This data can be submitted directly to be included without any other table
• You have no setup and configuration options, which are tweaked, therefore it is easy. You are basically outsourcing Server Maintenance and Database Maintenance Tasks. Whatever you are doing to a lower degree, if you live with the hosted SQLServer solution. And I do not know about hosting shared SQL Server, but I have had a bad experience with shared MySQL hosting in terms of continuity of performance and availability issues.
• Simple IDB claims that: Better availability with all data automatically copies in the data centers and all servers in your cluster freely read and write if any entire data center becomes dark or if a router Literally melts, your app may still be lukewarm, perhaps with a degraded service level, but fully functional if you planed it well And when the problems are fixed, the data is automatically synchronized in the background.
• Good performance is not as fast as the locally hosted SQLServer instance, but it is easily enough for user data (and more) outside of the box and it is well enough Scale from.
• If you app on your ASP.NET an Amazon EC2 Windows Server, you receive faster data transfer between your server and SDB. Normal round trip ping time is between 2 MMS and 7 MMS.
• Free use level covers 1 GB of bandwidth, 1 GB of storage and 25 hours of box usage per month. Depending on the app, you can go very far for free.

Losses include:

• There are no links or obstacles or schemas, so that you denormalize for a degree the restrictions you want to see , They should be done in code and you must be involved so that the simulations will need to be emulated. Adds to follow-up questions and the poor as the primary key is not as bad as the SimpleDB is a solid query API and is optimized for concurrent requests.
• You do not need setup and configuration options.
• Even very complex time can be simulated (equivalent time of) 2 round trip for SimpleDB.
• You have to be able to cope with the final compatibility. You can always apply a nuclear update and delete it at the item level, but updates can not show in the read requests for the complete second during normal tasks. (In my experience, not guaranteed). And of course, too much during the failure scenarios. "Working with it" should usually be at the session level if a user updates their profile (using their app) and nobody else is okay to see the change for a few seconds, but if they If the scene returns back to the old state for a few seconds then it will be bad. There are some easy ways to deal with this, but you have to think about these issues and deal with them.
• You may not be bad at the mercy of Amazon, and it is not necessary to be dependent on the mercy of a host of SQL Server, but it may be a reason for some people. Worse than the SQL Server case: If you are part of the company with Amazon, then a Simplified App is not going to work anywhere else (except for the M / DB example locally).