« Cloud Computing Business Considerations - Overview | Main | Connectivity - Client, server and user locations »

11/19/2011

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

douq millar

Perhaps a hybrid approach is to provide standard customization options in a controlled manner. In particular, your example of a custom database could be tied to a configuration file (controlling backup, mirror, performance, etc. options). So the custom database is added, but handled by cloud provider in the same standardized ways as the builtin databases. Identifying the most common requirements for customization might yield a 80-20 situation, where a few customizations, via the configurable approach, can accomplish most of the cloud clients' requirements.

douq millar

Another approach might follow the example of add-ons in complex software, especially also following the patterns of sandboxing. Photoshop, Firefox, Visual Studio, and others define highly restricted add-on code modules, dynamically load with only a few well-defined APIs, that allow fully customized code (the sandboxing would have to restrict I/O access, so only a few component library (like Java libraries available in browsers). Again just a few touch points in the standard system might easily handle the majority of customization requirements.

The comments to this entry are closed.


Cloud Computing Journal
Top 100 Cloud Computing Bloggers