Choosing Open Source Solutions
Part of my job is finding and testing open sourced solutions for already prominent commercially available software. The concept is simple: If it's open sourced, it can be customized, be platform independent, and it can be free. In the business world, this poses two key benefits. Having software that can be customized means fewer problems and more functionality. Getting it for free means lower cost for the services we provide to our customers, and having more money to spend on employees and infrastructure. As simple as this sounds, finding the right fit can be a laborious task of trial and error. Part of my job is minimizing the trial and error.
Finding the right open source product is just as important as the decision to use an open source product to begin with. In every business software environment there are a few common components. There is the commercial product we've all used for years. There are the two or three popular open source alternatives, and there is a list of migration headaches we all experience that eventually becomes the list of reasons why we should stick with what worked before. Occasionally there is a product that inspires us to stay in the fight. A classic example we can all relate to is a product most of us use all day, every day: the email client.
Transitioning from the industry standard email server and its client software has its pros and cons. The obvious benefit is cost. Purchasing server software can get very expensive very quickly. This cost usually grows as your company grows. The client software is usually purchased with a per user license that will also continue to grow in costs as your company grows. Or it's purchased by site license which is often only slightly less expensive. The greatest challenges faced with open sourced alternatives are functional dependence and data migration.
The majority of office software users in general have been using the same solution suite for several years now. Shortcut keystrokes have been memorized and feature dependency has become ingrained. This becomes a real challenge for open source solutions. Often, when new solutions have been introduced to market, deployment was met with end-user opposition. When the first prevalent open source email clients were released, a few were championed as the replacement cure-all for the mainstream standard. It wasn't long before users began to learn that features they had become accustomed to were either moved and renamed, or missing all together. The lesson learned was that the economic benefits of a software package are lost on a user who cant get past how much they dislike using it.
In choosing an open source solution, often there will be the commercially available product that meets all of your needs, and the open source products that will meet most of your needs. Occasionally there will be an open source product that either matches the functionality that the end user has become dependent on, or that adds a function that makes the loss of a feature acceptable. When our company made the decision to begin using the Zimbra email server and client, two of the deciding factors were its platform independence and its migration ease. The email client is available for a wide range of operating systems, including the commercial ones. While migrating emails, folders, calendars and contacts can get a little tricky, depending on which client you are importing them from, they've all made it so far. After that, migrating an account from one machine to another (regardless of the operating system) is an absolute breeze.
When you're evaluating open sourced software you have to remember that there will always be two perspectives you have to keep in mind. If you're considering it from an IT/Management perspective, if you look hard enough, there will often be a program that meets your platform requirements, is easy to install, and is free. Doing your homework also means evaluating them from the end-user perspective. It's easy to say "they're just going to have to deal with it..." but this more often than not leads to a decrease in productivity in the least, and at worse a full fledged mutiny. Few things are more frustrating than pitching a change and then having to go back to the drawing board when what seemed like a good idea fails and requires reverting back to something you decided was worth leaving in the first place. A little expansion on the evaluation will usually lead to much less trial and error, and ultimately a better fit in the long run.
Chase Crum is the IT Infrastructure Manager for Voicenation and a self-proclaimed Linux FANATIC.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide