A Product or Service bearing the “OSGi Enabled” ingredient mark signifies an ongoing commitment: a commitment to maintainability, flexibility, evolvability; a commitment to longevity.
The US DARPA agency states that the longevity of modern software systems is orders of magnitude less than other human built artefacts. In this, DARPA rightly recognise the need for software systems to be adaptive to unforeseen changes in their runtime environments. Via the BRASS initiative, DARPA hope to encourage the IT industry to think about bigger picture.
If you accept DARPA’s concerns; then the following conclusion is logically inescapable.
Adaptive, Evolvable Systems need to be Modular Systems. By modular – we mean internal structural modularity. An opaque software BLOB deployed as a static Virtual Machine or Container Image is not modular; and does not qualify. Also, to allow for interoperability and interchangeability, the approach to modularity must be based on open industry standards: standards that themselves must have demonstrable longevity.
DARPA – the answer to BRASS is OSGi™.
Since its introduction in the late 1990’s, OSGi – “the modularity system for Java” has slowly diffused into just about every corner of the IT industry. Originally create to address the resource and maintainability requirements for the Smart Home and IoT (circa 2000), OSGi has evolved and adapted and is today, in 2016, still uniquely positioned to address the issues and challenges that exist for the IoT, M2M, Smart Home, Smart Cities, Smart Agriculture markets.
Yes; an industry standard conceived in the late 1990’s is today directly addressing the commercial issues slowly being uncovered by the latest wave of IoT, including but not limited to: Analytics and Behaviour everywhere (Edge, Fog, Mist, whatever); the management of multitudes of heterogeneous and continuously changing Edge devices; secure software deployment to those devices; deploying only what is necessary and knowing the pedigree / providence of each atomic unit of software deployed.
This week the OSGi Alliance launched the OSGi™ Enabled ingredient mark. Probably long overdue; but in a decade’s time this may well be one of the most recognised ingredient marks powering the Adaptive / Pervasive Internet of Things. It will need to be if DARPA’s challenge is to be addressed.
So what does “OSGi Enabled” signify?
The Product or Service bearing the “OSGi Enabled” ingredient mark has been engineered with maintainability, adaptability and evolvability as design priorities.
The “OSGi Enabled” mark also indicates that the solution provider realises that open industry standards are both required, and that they do not just spontaneous appear. Effort and resources are required to create such standards; and the vendor, by supporting the OSGi Alliance, is actively playing their part in that process.
Paremus have been an OSGi Alliance Strategic Member for many years, and we have contributed in many areas across the organisation: President (2011-2013), Treasurer (2014-current), VP Marketing (2015-current), IoT co Chair (2015-current). Paremus have also driven or contributed to many OSGi Specifications.
The Paremus Service Fabric – a highly modular orchestration platform for Enterprise or IoT environment – has been built from the ground up leveraging OSGi. In addition Paremus extend OSGi principles beyond Java with Packager (see https://docs.paremus.com/display/SF113) – to support Microservices or traditional software components written in an language.
Hence I’m delighted that Paremus Service Fabric is eligible to use the “OSGi Enabled” ingredient mark and all that this signifies.
Dr Richard Nicholson. Paremus founder & CEO, OSGi Board Member.