as Andrew mentioned, Azure Storage and SSDS are very BigTable like.
SSDS seems to have more querying capabilities but I guess we'll have
to test the performance. Both can also store blobs up to 50GB in size.
Worker Roles are nice, long running processes that are fed by a queue.
Web Roles (like GAE request handlers) can feed the queue for off line
or async processing. this mixed model of execution is missing from GAE
(and was not on the roadmap either)
.Net Services - Access Control and Workflow are nice features as well
some questions:
performance - really can't comment until I test it but how fast the
datastore works is really my biggest concern
indexing - how will they handle the same "exploding index" problem
that GAE has. Is it automatic (seems to be)? SSDS looks like it can
query using inequality/group/sort operators, hopefully on multiple
entity properties
VM caching/startup - WebRoles/WorkerRoles have dedicated physical
cores associated with them but it is unclear how Azure will auto-scale
your instances. (the CTP will not have this, its controlled via config
file). Cold startups of GAE instances are becoming an issue for me as
more modules need to be loaded (lazy loading as much as possible too).
How will Azure handle this? Will your .Net apps be pre-jitted/
optimized before upload? How often will they be swapped out of the
fabric? If you can maintain a minimum number of instances, how would
we be charged for idle time? In GAE, it would be nice if we could keep
several instances active
pricing - the whitepaper says per CPU/Storage/Bandwidth, so very GAE
like. I would assume the pricing between the two will eventually be
the same
another interesting though is that Azure runs any .Net runtime
language so in theory, you should be able to port the GAE stack to
IronPython and have it run on Azure. this would likely take a large
effort to build the abstraction layer but having a secondary cloud
infrastructure to run apps on would be nice
MS seems ot have been working on this for awhile (a couple years) so
it might actually be workable at V1.
cheers
brian
On Oct 27, 3:12 pm, "Andrew Badera" <
and...@badera.us> wrote:
> Or, if you're talking about SSDS (SQL Server Data Services) already, be
> aware, they're a BigTable clone ...
>