Independent Software Vendor


According to National Institute of Standards and Technology, cloud computing is a model for enabling convenient, on demand network access to a shared pool of configurable computing resources (eg: networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

Cloud computing architecture of a cloud solution is the structure of the system, which comprises on-premise and cloud resources, services, middleware and other software components. The factors to consider by ISV’s looking at cloud computing architectures are:

  • Availability & Reliability – Group the applications based on the need for availability. Depending upon the availability requirements, the service provider needs to be appropriately chosen. Multi site, disaster recovery, mitigation plan play crucial roles. Performance in terms of vertical scaling, horizontal scaling, multi-site, network capacity etc also need to be evaluated
  • Security – Loss of sensitive data, data storage security, addressing data standards compliance are some factors. Where the data will reside, who can access what, how the vendor controls the data etc. play a major role in performing audits and ensuring compliance.
  • Manageability – Accountability for the customer and vendor need to be clearly defined.

 While there exist many sub factors, the factors written here are critical and cannot be ignored while considering a cloud computing architecture.

~ Ramya

Advertisements

ISV’s Perspective on Infrastructure, Platform, Technology and Back-end Integration

An ISV instead of trying to focus on developing everything  from scratch can take advantage of the Infrastructure-as-a-Service and Platform-as-a-Service being offered by different companies.  SaaS requires an architecture that can support peak usage demands and process millions and millions of transactions in a secure and reliable environment.

Choosing the right technology is a key to user adoption. Many transitioning ISV’s choose a well known technology stack to keep away from risks due to obsoleteness.

It is very essential for an enterprise SaaS application to be able to integrate with other applications. With SaaS not only does the core application need to function, but it needs to function in conjunction with other systems. Following a centralized approach for code management and focusing on open standards  helps avoid integration problems.

(Source: SaaS Attack & Salesforce.com)

~ Ramya

I have been talking to several people in the software products space and everybody feels that at a certain stage the product needs to be innovated in order for it to keep in pace with the competition. But when I asked them about what exactly do they mean by innovation there was no single answer. So my two cents worth on Software Product Innovation.

What is Product Innovation?

It is adding something new which would be beneficial to both the customer and the vendor. Product innovation for the software vendor is mostly process innovation for the customer.

How does Product Innovation take place?

Product Innovation lies in the hands of a team and not an individual. Brainstorming sessions are an integral part of Product Innovation. It usually starts with Idea generation, Research, Experimentation and Prototyping. Usually vendors look for ways of solving customer problems which results in an idea being generated.