Adapting your development processes for the Cloud
Tuesday 25th February 2014
Whilst the main reason Cloud is taking off is down to new applications going to market in far less time, it is also expected that products are updated in much faster cycles than under traditional systems.
As an example of this, compare Microsoft's Azure offering with many of its other products. While typically Microsoft updates its product offering roughly every year, for Azure this is every three months.
This demonstrates how much faster the rate at which developers need to release updates within the Cloud. Indeed, independent software vendors (ISVs) must be able to keep up if they want to remain competitive in the current climate.
To aid them with speeding up the development process, they need to fundamentally change the way that they complete tasks. Rather than updating a whole product at once. In the Cloud, they need to be able to break down their challenges into a range of smaller tasks. If ISVs can do this then they will be able to produce better updates in less time.
With development cycles speeding up, the needs of various Cloud projects will be changing all the time. As a result, the best bet for ISVs to keep up with this is to continually test and evaluate their products at the same time as designing new applications.
This will be easier to do if they have broken their development tasks into a range of smaller duties, making their tasks much easier to compare.
The benefits of this approach are two-fold. Firstly, by having a parallel approach to development they will be more likely to ensure better functionality when they come to deliver a final product or an update. Secondly, the chances of having to rush changes close to the deadline for delivery will be dramatically reduced as problems will have been tackled in tandem with other duties.
Last minute rushed changes can be fatal for products delivered in the Cloud as updates need to be functional and streamlined to keep customers interested.