Azure also has SQL as a (more expensive) option, which, for some applications, is a very compelling choice over Azure and GAE's table storage. If you don't need it, though, it shouldn't factor into your decision.
I'm sure there will be whitepapers galore, and there are some significant differences under the hood, but it probably most comes down to what toolkit your developer is familiar with. On Jul 15, 11:08 am, mytemp <[email protected]> wrote: > Ah, thanks, wanted to make sure that wasn't SPAM, I am looking for > Python/GAE expertise, I'll post another message then. > > Azure pricing was announced yesterday and causing me to rethink doing > Azure, I have access to a rockstar .NET programmer at a reasonable > price, so I was on the fence as I prefer GAE/Python and I used to do > Python so being able to read it is useful ;-) Also, there are a few > GAE things I like more (like I don't have to decide when to scale or > how many instances, I just set a quota, and worker threads are only > charged when executed and not constantly when in a while loop). > > So, if I had access to a rockstar Python/GAE person (or two)... at a > reasonable price, I think I'd just go GAE. Anyone? > > On Jul 15, 7:05 am, Adam <[email protected]> wrote: > > > > > And the second part of your question: Azure vs. GAE. I'm not aware of > > any formal white papers that exist on this subject; although, I'll > > wager cash money that Microsoft has a couple in the pipeline > > somewhere. I work with both. I earn my salary being a happy trilobite > > in the Microsoft ecosystem, so I have the C# and ASP.NET skills to > > take good advantage of Azure. I'm also a hopeless Google fanatic, and > > I got on-board with GAE on day one. > > > My analysis: Azure and AppEngine are more like each other than any of > > the other cloud computing platforms, such as Amazon's EC2. They both > > give you a new programming model -- a sandbox -- to work in that > > encourages you to architect your applications in a way that allows > > them to take advantage of the instant, no-effort, on-demand scaling > > that is the real, compelling advantage of the Cloud. > > > They both give applications fairly generous free quotas that give the > > developer and extremely-low cost-of-entry, enabling him of her to > > build and deploy an application without up-front and.or monthly cash > > outlays. If you are lucky/smart your application can be generating > > enough revenue to more than cover its costs before you have to start > > paying for resources. > > > The main decision point between the two platforms comes down to the > > technology that you want to use to build your web application. Do you > > have access to C# and ASP.NET skills? Azure is a good choice. Do you > > have a Python/Java open source guru handy? AppEngine is a winner. > > > A secondary decision point might be your choice of development > > platform. The Azure SDK will install and run on Vista or Windows > > Server 2008, and you will need a Visual Studio 2008 license. On the > > other hand, you can build AppEngine applications on Windows (XP, > > Vista, 7, etc), MacOS or Linux. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
