Demystifying open source

There is a lot of hype surrounding open source currently. Most organizations view it as a one-stop answer to all their infrastructure problems, while shoring up on costs. This is partially true. 

Assimilation of open-source based applications can reduce infrastructure costs, and these programs are likely to be less susceptible to security threats as compared to their proprietary predecessors. 

Talking about Linux's rampant adoption in India, Mark Rais, Editor-In-Chief of reallylinux.com notes “It is entirely likely that rate of Linux adoption in India is a symptomatic response to a much more deeply rooted and inherent socio/political characteristic. In India, although regional diversity exists, although unique political structures and class structures compose the foundation of business and law, the principal that Linux can be used as a device for independence and achievement is understood.”

This is why solution providers should give serious thought for getting themselves and their team trained on open-source, so that they can develop customized applications to suit the needs of their clientele. They can leverage on the current interest about this subject and highlight how open-source applications can help improve a company's productivity and cost efficiencies. 

Why open source makes sense

The biggest argument in favor of open source is that it is not governed by any single entity. Any programmer can work on a code and then develop applications based on it, which can be freely distributed. These programs can run on single or multiple platforms like Windows, Unix or Linux. 

According to Open Source Initiative (OSI), a non-profit organization “when programmers can read, distribute and modify the source code for a piece of software, the software evolves. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing.”

Linux is become the flag bearer of the open source movement and part of it is because it works on multiple platforms. While most people think that it is the be-all and end-all of all open source applications, this is not true. 

There are others like Apache, a common web server available on several platforms. Mozilla is another open source-based web browser and toolkit, designed for standards compliance, performance and portability.
MySQL, another application, is the most common database used on the Linux platform. 

There is also JBoss, a J2EE application server and Simple Mail Transport Protocol, a mail server application. One can't forget
Zope, which is a content management solution.

Business advantages of open source 

The sole winning point in favor of open source is the fact that it is now owned by any single entity. Since it is freely available, any programmer can read and improvise on it. And since there is a whole community backing it, coders proactively fix any bugs that might reside in the program. This means, there is a vast bank of people who are constantly working on the source code, improving it and helping it evolve. 

This translates into a major business advantage. Companies designing their own open source applications can rely on this widespread network of programmers to help them fix any problems with the application, without having the same people on its payroll. Of course, it has to take care to see that the primary code is not revealed, lest some coder changes it inadvertently or maliciously. And with so many people across the globe willing to work on the application, the software related problems could be resolved quickly.

Who stole my code?

One of the biggest concerns that companies who design open source applications is security. Since all the development is done on a freely available code, how can the developer be assured that the source code won't be a victim of industrial espionage? And how can it ensure that some other company does not profit from the enhancements that it has made to a code?

Well, for starters, the company can desist from divulging the primary code and should only post the auxiliary programs online. Also it can apply to the
OSI, which gives licenses to various open source applications and even certifies them. 

This ensures that while the community can make value-added changes to the code, others do not solely profit from the enhancements. Currently over 50 licenses are currently in existence, with their independent terms and conditions.

Where partners get into the fray 

Anyone who knows to code programs can create codes on open source. So if you are a solution provider, it makes sense to develop a team of programmers who can design applications that can be installed for your clients, based on it. And you can sell your code as well. 

However, since the very essence of open source means that anyone can sell your code as well, as an entrepreneur, your USP comes in when you create a value add to the applications, either in the form of service, updates or a certification mark testifying to its quality.

There are a number of companies worldwide that operate on the open source model. Most, like Red Hat, charge little for the license fees and instead rely on service as a revenue stream. This encompasses consultancy, installation, training and support.

Creating a similar business module is not as difficult as it may seem. All you required is a qualified set of programmers who can isolate the correct piece of code and then develop it to create applications that will be on intrinsic value to your customers. You can start with a sample application and build your portfolio of offerings as you go along.

Paying for the service might not seem like a viable revenue stream for some customers, initially. This was one reason why the open source movement took its time to catch up. But as it gains momentum, the mindset will change and there will also be a lot more people who will have qualified to offer support. So the cost efficiencies will give the adoption of open source a shot in the arm.

Thumbrules for open source applications

While designing open source applications there are several guidelines you have to bear in mind. Firstly, consult with your customers why it is viable for them. You can illustrate cost savings by using this example. 

In an infrastructure diagram, you have the operating system as the backbone, with the database sitting atop it and the applications topping the pyramid. The bottom layer, i.e. operating system, is available on open source, which reduces the cost of the infrastructure by one-third. Customers prefer paying for their database servers and software. Most applications are also proprietary in nature. 

Now, if the latter were to be based on open source, then the company saves two-third of its infrastructure costs, as two layers of its infrastructure architecture are non-proprietary in nature. Initially, it can use only some open source-based applications to appreciate its cost efficiencies, before making a complete transition.

Once your customer decides to take the plunge and you start working on open source applications, ensure that these can be integrated with legacy systems. Its ease of integration should allow it to be used with a wide range of application development tools.

But make sure that you offer indemnification to your customers, so that even if they move to another solution provider, their applications are supported. This will only boost your customer's morale and it is more than likely that he will prefer dealing with you, rather to switch loyalties.

VINITA BHATIA 

MUMBAI