When discussing the pros and cons of open source software (OSS), most people will immediately list legal or security risks with OSS as huge cons. But the truth is the risks are no different than using commercial software. If you violate a commercial license or if the commercial software you use has a security flaw (and we all know commercial software is full of security issues) than the same could be said about commercial software in general. But the truth is you have to be smart about OSS. You have to understand why it’s important to know where it came from, how it’s licensed, and how to use it to lower your risks, just like you do with commercial software.
In the time that I have spent with OpenLogic, I have worked with companies across many industries, and with companies ranging from a handful of developers to thousands of developers. One thing they have in common is that they typically have some type of open source policy, some far more developed than others.
I have been a developer for a number of years (yes, it’s a large-ish number) and I’ve worked on teams that have developed software on commercial platforms, on teams that have used a mixture of open source and commercial components, and on teams that have used primarily open source. Overall, I’ve developed (no pun intended) a preference for using open source tools and components whenever it’s feasible. Here are some of the reasons why I prefer to develop with open source code:
As a COO, and former CFO, I’ve been in charge of my fair share of commercial and open source software projects over the years. A couple of the projects I was directly in charge of the design of features, while others I held responsibility to sign off and approve at a high level. Some projects were minor, while others involved full-scale customizations between an accounting application and a CRM application, with a front-end web interface. Although the custom implementation worked great, and if I might say were pretty ingenious, there were definitely some valuable lessons I’ve learned over the years the hard way, that can be valuable to others in the same situation.
This post is part 2 of a 3 part blog series that will look at leveraging Apache Tomcat clustering, in order to increase your system’s availability.
When most people think "open source database," the first name that comes to mind is MySQL. This relational database management system (RDBMS) has been around for 17 years, and in that time it has become intimately associated with the open source ecosystem, notably as a component of the LAMP stack used to build solid web platforms - the Linux operating system, Apache web server, MySQL database, and PHP. But MySQL also serves as the back end for prominent projects such as WordPress and MythTV, and it's used by enterprise customers such as Facebook, Sears, and BBC News.
Yesterday we had the pleasure of attending the “Meet Windows Azure” launch party, along with a number of other Azure partners in San Francisco.
Open source is all about choice. Over the years, OpenLogic has grown and thrived in part because our mission is centered around giving that choice to corporations —the flexibility to choose the best open-source tools for any job, as well as the support they need to confidently deploy and maintain open source across the network.
If you read a post on The Enterprise OSS Blog, please leave a comment. Let us know what you think, even if it's just a few words. Comments do not require approval, but they are moderated.OpenLogic reserves the right to remove any comments it deems inappropriate.