A CoreCollective initiative was launched today, encouraging software developers that build tools and applications that run on Arm processors to work more collaboratively.
Created by Arm in collaboration with Linaro, a provider of software engineering services, the CoreCollective ecosystem includes Ampere, Canonical, CIX Technology, Fujitsu, Google, Graphcore, Microsoft, Qualcomm, Red Hat, Samsung and SUSE.
Andy Wafaa, senior director and fellow for the software community at Arm, said the goal is to standardize open source tooling and integration workstreams that, in addition to reducing the overall amount of technical debt that software engineering teams building software for Arm processors create, also serves to make it simpler to port applications between instances of Arm processors.
There is no cost to join CoreCollective, which will soon be adding additional members to expand the overall size of the ecosystem, said Wafaa. Specific focus areas will include Android, data center, confidential compute, edge, Linux fundamentals, virtualization and Windows on Arm.
Most Arm processors are created by multiple foundries that have licensed a design, with each provider either providing their own software development tools or encouraging third-party providers to build them. That approach, however, creates silos of ecosystems that in many cases are building redundant libraries and tools that over time unnecessarily increase the total cost of building software, noted Wafaa.
Arm is hoping that the amount of software technical debt that each manufacturer of an Arm processor is creating will ultimately be reduced, he added. Once better aligned, the total cost of building Arm applications should naturally be reduced.
Mitch Ashley, vice president and practice lead for software lifecycle engineering for the Futurum Group, said a neutral, open framework for standardization being advanced under a CoreCollective ecosystem is an indication of growing Arm momentum. With Google, Microsoft, Red Hat, Qualcomm and others co-investing in this layer of system software, there is a growing sense of mutual shared interest across the Arm community, he added.
DevOps teams, of course, have a vested interest in that effort because Arm processors are now being more widely deployed in everything from mobile devices to cloud computing services. The challenge is that unlike x86 platforms, there is no overall ecosystem for building software that can run across multiple implementations of Arm processors. Of course, the x86 ecosystem has been building out its software ecosystem for several decades so it might be a while before the Arm community catches up.
It’s not clear what percentage of platforms today are based on some type of Arm processor but the need to unify the software engineering ecosystem that is emerging around them is becoming more acute. Most applications are inherently distributed. If each environment has a different set of tools and libraries, building, deploying and maintaining distributed applications only becomes that much more challenging.
In the meantime, DevOps teams should be expecting to encounter a lot more Arm-based platforms in the months and years ahead. After all, the days when organizations committed to one class of processors on an end-to-end basis are now officially long over.