I think that’s a wise idea.
Especially if you mean instead of building your own custom system you are using cloud based systems to build your solution?
Why re-invent the wheel.
i am thinking of using salesforece.com instead of building my own develompment cloud.
Why? What do you need to do with it? Without knowing the purpose, it’s hard to have any thoughts at all.
For example, if I’d use SalesForce just for storing/retrieving basic customer relations info, I’d probably just install SugarCRM and do it myself instead. But if I had multiple, scattered remote locations and a need for high reliability and quality, I’d start to lean towards a service like SalesForce.
If I was going to experiment with development for cloud services, I might even go with three different implementations at once — SalesForce, some general cloud alternative and my own implementation of something like Eucalyptus. When I’m developing, I prefer knowing what might be ‘standard’ as well as what extensions might be possible.
But it’d help to know what the thing is expected to provide.
>>Thinking of using
Until you crystallise what your environment and requirements are, you just keep thinking.
“I’m thinking of buying a car /boat/ aeroplane – which do you think would be best?”
needs more input…