Language Selection

English French German Italian Portuguese Spanish

Linux Levels the OS Field?

Filed under
Linux

Q: What's the current status of Linux/open source adoption in financial services?

A: Guru Vasudeva, Nationwide: Adoption is increasing [because] ... people are finding that it's not just an economic driver anymore to save some licensing costs. More and more people are skilled in the marketplace in these open systems rather than in traditional, proprietary systems. There are definitely some obstacles to adoption, such as the increasing complexity of licenses that are attached to these open source systems. We started off with two or three different licenses and now there are at least 60 to 70 different types of open source licenses around, and they are conflicting with one another. So it's definitely a concern for companies to make sure that they are not undertaking too much risk in this space.

A: Bill Hartnett, Microsoft: Linux is seen as a good alternative to proprietary versions of Unix. Running on commodity hardware, it has many of the same advantages of Windows and is sometimes an easier migration path off of high-cost infrastructures, such as Solaris or AIX. The growth of Linux as a Unix replacement has been strong, but as the easy migrations are completed and the true costs of Linux come into focus, the pace is leveling off, if not declining. The exception may be in mainframes, where legacy costs are still very high.

A: Chuck Johnson, Oracle: Insurers are steadily adopting open source software, especially Linux operating systems (OSs). Penetration is generally faster in Asia Pacific and EMEA, with companies such as LIC of India and MACIF, a major European personal insurance company, embracing Linux. In North America, many insurers are exploring Linux to reduce cost and increase flexibility, often working with Oracle or IBM. With the recent advent of open source liability insurance, insurers are more likely to take a risk on open source copyright issues. Ultimately, insurers will gravitate toward consistent, open source OSs backed by large commercial company support structures.

Q: What are the most important considerations for insurance companies in terms of selecting/standardizing on (a) particular operating system(s)?

Full Story.

More in Tux Machines

Linux Foundation: New Members, Certifications and Microsoft Entryism

ETSI/GNU/Linux-based MANO

  • ETSI Open Source MANO announces Release FOUR, moving faster than ever
    ETSI is pleased to announce the availability of OSM Release FOUR. Bringing a large set of new features and enhancements, this version is the most ambitious and innovative OSM Release to date and constitutes a huge leap forward in terms of functionality, user experience and maturity. This new Release brings substantial progress thanks to a number of architectural improvements, which result in a more efficient behaviour and much leaner footprint – up to 75% less RAM consumption. Additionally, its new northbound interface, aligned with ETSI NFV work, and the brand-new cloud-native setup, facilitate OSM’s installation and operation, while making OSM more open and simpler to integrate with pluggable modules and external systems, such as the existing OSS.
  • Open Source MANO Release FOUR lands
    In monitoring, ETSI says OSM Release FOUR's alarm and metric settings are easier to use, and a new policy manager adds push notifications and reactive policy configuration, which the standards body says “opens the door to closed-loop operations”. The monitoring module uses Apache Kafka as its message passing bus, and the module also implements a flexible plugin model so sysadmins can BYO monitoring environment.

today's howtos part 2

Programming: GitLab, Security, Power and Jakarta EE

  • GitLab 10.8 open sources push mirroring
    GitLab 10.8 was released this week with the open sourcing of a highly requested feature. The company announced its push mirroring capability is now open sourced. Push mirroring was originally introduced as a paid feature, but GitLab says it is one of the most frequently requested to be moved into the open-source codebase. This move will add a few new use cases for GitLab Core users, such as freelance developers being able to mirror client repos and users migrating to GitLab being able to use push mirroring to ease the migration path.
  • How Security Can Bridge the Chasm with Development
    Enhancing the relationships between security and engineering is crucial for improving software security. These six steps will bring your teams together. There's always been a troublesome rift between enterprise security teams and software developers. While the friction is understandable, it's also a shame, because the chasm between these teams makes it all the more challenging to build quality applications that are both great to use and safe.
  • Which Programming Languages Use the Least Electricity?
    Can energy usage data tell us anything about the quality of our programming languages? Last year a team of six researchers in Portugal from three different universities decided to investigate this question, ultimately releasing a paper titled “Energy Efficiency Across Programming Languages.” They ran the solutions to 10 programming problems written in 27 different languages, while carefully monitoring how much electricity each one used — as well as its speed and memory usage.
  • How Java EE found new life as Jakarta EE
    The title of this post may seem strange, but if you look a bit into Java EE's recent history, it will make sense. Originally, Sun started and ran Java Enterprise Edition, and later Oracle took over after it acquired Sun. Specifications were driven by a Sun/Oracle-governed process. At more or less regular intervals, they made a new version of the specification available, which was implemented by the server vendors. Those vendors had to license the technology compatibility kits (TCKs) and brand from Oracle. Let's fast-forward a bit. In 2013, Java EE 7 was released, and Oracle began work on EE8, but it did not progress quickly. Meanwhile, new technologies like Docker and Kubernetes came along and changed the way applications run. Instead of running a single fat server process on a big machine, the software is now split into smaller, independent services that run in a (usually) Docker container orchestrated by Kubernetes.