Cloud hosting solutions company Pulsant gets down to the nitty gritty more than some firms. Rather than spending an excess of time meandering around the oh-so worn out subject of ‘business transformation’, the firm appears to enjoy talking more directly about the real mechanics of software application development in the as-a-Service world.
It’s an as-a-Service world after all
Tom Brand, business development manager at Pulsant explains that in the transformation from ISV to SaaS provider there are many areas that need to be looked at, from shifts within the organisation itself, like culture, to changes in operations, such as sales and marketing approaches, remuneration models and in the actual solution itself.
“Changing and adapting the solution is where developers play the most important role. They need to be clear on what this transition entails — a few tweaks to transform legacy code and applications to be cloud ready, or a complete rework to deploy a cloud native solution,” said Brand.
He advises that ISV developers have to think about what changes are needed to get their existing applications to serviceable offerings. This gets a bit more complex if the process involves more than making a few tweaks to those legacy applications, moving from a pre-packaged app to something that needs to cater for a multi-tenanted environment.
Fruitful tools from cloud providers
“If a complete rework is needed — the difference between making something cloud ready and creating an app that’s cloud native — then working with cloud providers and using the tools they offer can be fruitful,” said Brand.
He explains that in essence, by taking advantage of these tools and removing technology from the critical path, developers can focus on what they’re good at, which is innovation.
By not worrying about the platform, developers can create the apps, write the code and incorporate the required functionality that will help them deliver the needed solution to their customers, and ultimately to their end-customers.
Pulsant’s Brand concludes by saying that traditionally, DevOps focused on using a large team to accomplish a goal or work on a single project.
“But increasingly different ways of working — like the micro-services architecture approach — are being used where smaller, more agile teams work on smaller apps that function independently, but also form part of the bigger picture. This means more control, better flexibility and managing the entire team together with a unified approach to building the platform, deploying it to enable a clear focus on the service functionality that sits on top of it,” he said.