Personally, I think it's more useful to split the cloud into it's 2 aspects:
- compute cloud. High latency, high performance, long-running processes. Suitable for questions like 'what is the meaning of life', 'what is the economic forecast for austria' etc.
- app cloud. Rapidly scalable, low-latency, short processes. Suitable for running a website or anything that requires huge scalability at short notice.
Mixing the 2 leads to less than optimal results.
Personally, I am expecting 'XBL gold' to be renamed as 'one cloud' (or something like that), and various features of 'app clouds' to be added. (storage, music, live data, access to large datasets etc).
In terms of 'compute cloud', I'd expect all kinds of interesting kinect usage, otherwise not much.
IMHO "cloud compute" can be seen as a higher latency, less reliable version of GPU compute - and GPU compute is something that most devs haven't got to grips with yet.
But I'd love to be wrong, as this stuff greatly interests me .
- compute cloud. High latency, high performance, long-running processes. Suitable for questions like 'what is the meaning of life', 'what is the economic forecast for austria' etc.
- app cloud. Rapidly scalable, low-latency, short processes. Suitable for running a website or anything that requires huge scalability at short notice.
Mixing the 2 leads to less than optimal results.
Personally, I am expecting 'XBL gold' to be renamed as 'one cloud' (or something like that), and various features of 'app clouds' to be added. (storage, music, live data, access to large datasets etc).
In terms of 'compute cloud', I'd expect all kinds of interesting kinect usage, otherwise not much.
IMHO "cloud compute" can be seen as a higher latency, less reliable version of GPU compute - and GPU compute is something that most devs haven't got to grips with yet.
But I'd love to be wrong, as this stuff greatly interests me .