A Fault Tolerance Concept for Distributed OSGi Applications - Fabian Meyer

Sep 21, 20111 like2,124 views

Computer systems are becoming increasingly complex. This makes it more and more difficult to ensure their correct operation and to correct errors promptly. Due to their increasing use the focus of this work is fault tolerance for OSGi-based, distributed applications. The designed concept increases the reliability of such applications while it remains perfectly hidden and doesn't interfere with their normal operation. A service that has been made fault tolerant using the developed concept does not differ from any other OSGi service and can be used in the exact same way. To achieve fault tolerance, redundant instances of the service are distributed among several nodes. Each replica is given a special role, which is either active or passive. Active replica process service calls, passive replicas take their place in case they fail. How many replicas to use and what their specific role is can be configured according to the needs of any service. A proxy is used to consolidate service calls and relay them to the corresponding service instances. It analyzes every call and their result allowing the tolerance of hardware and software faults. The concept is designed to only use standardized OSGi interfaces and procedures. To identify the replicas of a service and what framework they are running on the RemoteServiceAdmin from the OSGi Enterprise Specification was used. It allows an imported service to be mapped to its origin. The described concept is available for free from the web server of the distributed systems lab of the Hochschule RheinMain.

A Fault Tolerance Concept for
Distributed OSGi Applications
Patrick Deuster, Fabian Meyer, Reinhold Kröger

RheinMain University of Applied Sciences

September 21, 2011

OSGi Alliance Marketing © 2008-2010 . 1
Page
COPYRIGHT © 2008-2011 OSGi Alliance. All Rights Reserved
All Rights Reserved

Agenda

• Motivation
• Related Work
• Approach
• Evaluation
• Conclusion

Page 2 OSGi Alliance Community Event 2011© 2008-2011. All Rights Reserved

Motivation

• OSGi is a commonly used service platform
• Distribution supported by Remote Service specification
in R4.2
• Remote Services can be used as a basis for a fault
tolerance concept

• Based on Patrick Deuster’s M.Sc. Thesis [1] at
Wiesbaden University of Applied Sciences

Page 3 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Requirements

• No modification of the underlying OSGi framework
implementation
• Transparency for service consumers
• Administration interface
• Configurable redundancy mechanisms
• Synchronization of replicas

Page 4 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Related Work

• DR-OSGi [2]
• Aspect oriented
• Caching, redundancy
• Major disadvantage: Can only be bound to local replica

• Towards reliable OSGi framework and applications [3]
• Proxy layer
• Service call forwarding to replicas
• Major disadvantage: Modification of the OSGi framework implementation

• FT-OSGi [4]
• Proxy layer
• Configuration and synchronisation
• Major disadvantage: No transparency for service consumers

Page 5 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Approach

• Redundant service instances
• Active and passive replicas
• Proxy layer
• Service call forwarding from proxy to service replicas
• Flexible result evaluation in proxy to determine reply to
caller
• OSGi Remote Service specification used
• Apache Zookeeper used for group communication to
establish consistent views

Page 6 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Architecture

Page 7 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Configuration Setup

Page 8 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Runtime

Page 9 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Performance Evaluation (1/2)

• Call time (2000 service calls)
Configuration Avg (ms) Min (ms) Max (ms) Std. Dev. (ms)

No Fault Tolerance 2,4 1 26 1,3
Setup:
1 Active / 1 Passive 7,1 4 64 3,6 CPU: Intel Core 2 6320
2 Active / 1 Passive 8,2 4 61 5,6
Phys. Mem.: 3 GB
Java: JDK 1.6
OSGi-FW.:
• Reconfiguration time (50 failovers) Eclipse Equinox 3.6
RS-Impl.:
Type Avg (ms) Min (ms) Max (ms) Std. Dev. (ms) Eclipse Communication
Service Instance Failover 11,1 1 30 7,0 Framework

Framework Instance 3881,9 3013 5391 687,7
Failover

Page 10 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Performance Evaluation (2/2)

4,1 ms

4,1 ms

Page 11 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Conclusion

• Design and implementation of a fault tolerance concept
for distributed OSGi applications
• Transparent proxy layer with call forwarding
• Automated replica distribution
• Active and passive redundancy
• Flexible result evaluation in proxy to determine reply to caller
• State synchronization between replicas

• Future Work:
• Detailed performance evaluation
• Utilization in real application
• Cooperation with industrial partners

Page 12 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

Thank you for your attention!

Questions?

Page 13 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

References

[1] Deuster, Patrick. Ein Fehlertoleranzkonzept für verteilte OSGi-Anwendungen.
Master Thesis, Wiesbaden University of Applied Sciences (2011)

[2] Kwon, Young-Woo; Tilevich, Eli; Apiwattanapong. Taweesup: DR-OSGi:
Hardening Distributed Components with Network Volatility Resilency. In:
Middleware (2009), 1-20.

[3] Ahn, Heejune; Oh, Hyukjun; Sung, Chang O.: Towards reliable OSGi
framework and applications. In: Proceedings of the 2006 ACM synposium on
Applied computing. ACM (SAC ´06).

[4] Torrão, Carlos; Carvalho, Nuno A.; Rodrigues, Luís: FT-OSGi: Fault Tolerant
Extensions to the OSGi Service Platform. In: Proceedings of the Confederated
International Conferences, CoopIS, DAO, IS, and ODBASE 2009 on On the
Move to Meaningful Internet Systems: Part 1. Springer-Verlag (OTM ´09)

Page 14 OSGi Alliance Marketing © 2008-2011 . All Rights Reserved

This document provides an overview of Jakarta EE 8 and the future plans for Jakarta EE 9 and beyond. It discusses how Java EE was donated to the Eclipse Foundation and renamed to Jakarta EE. It outlines the release timeline and key features of Jakarta EE 8. It also summarizes the goals and proposed changes for Jakarta EE 9, including renaming javax packages to jakarta and tooling updates. Finally, it speculates on potential new specifications that could be added to Jakarta EE in the future.

GlassFish 3.1 at JCertif 2011Arun Gupta

GlassFish Server 3.1 is the latest version of the open source Java EE application server. It provides improved developer productivity and manageability. New features include application versioning support, application scoped resources, improved monitoring, and clustering and high availability for HTTP, EJB, and other services. GlassFish remains focused on Java EE standards, open source development, and providing the best platform for building Java applications.

OSGi-enabled Java EE applications in GlassFishArun Gupta

Oracle Cloud Infrastructure：2020年8月度サービス・アップデートオラクルエンジニア通信

This document provides an overview of new services and updates for Oracle Cloud Infrastructure in August 2020. It describes the new Gen 2 Exadata Cloud@Customer X8M system, which features faster CPUs, more memory and storage. It also discusses updates to billing models for several services including switching some resources to per-second billing. The document lists various service updates in July 2020 related to networking, security, and databases.

GlassFish Community Update @ JavaOne 2011Arun Gupta

06 fse designMohesh Chandran

This document discusses fundamentals of software engineering design. It explains that design creates a representation of software that provides implementation details beyond an analysis model. Four design models are described: data design, architectural design, user interface design, and component-level design. Design principles, concepts like abstraction and patterns are explained. Tools like CASE tools can support design, and evaluation ensures a quality design. A design specification document formally specifies the design.

Getting to the Next Level with Eclipse Concierge - Jan Rellermeyer + Tim Verb...mfrancis

OSGi Community Event 2016 Presentation by Jan Rellermeyer (IBM), Tim Verbelen (imec) & Jochen Hiller (Deutsche Telekom AG) Eclipse Concierge provides a clean, small and lightweight implementation of the OSGi core framework specification, specifically tailored to embedded systems and IoT. In this talk, we will cover how to use and deploy the Concierge OSGi framework (e.g. using OSGi enRoute), and discuss many of the new and upcoming features in the Concierge project such as the OSGi REST interface and Cloud Ecosystems reference implementations. We will also present our work in progress on implementing the OSGi R6 core specification level and novel demonstrations that illustrate the advantages of having a lean and streamlined OSGi implementation to deal with deployment and dynamism in IoT applications.

Fault Management System (OSS)Riswan

GlassFish Server 3.1: Deploying your Java EE 6 ApplicationsArun Gupta

GlassFish Server 3.1 is the latest version of the open source Java EE application server. It provides improved developer productivity, clustering and high availability capabilities, and supports the latest Java EE 6 specification. Some key features include faster redeployment times, session replication for high availability, modular extensibility through OSGi, and enhanced management and monitoring interfaces. Oracle will continue to invest in GlassFish Server to deliver new Java EE versions quickly and drive further innovation in areas like hybrid application development.

Deploying Java EE 6 Apps in a Cluster: GlassFish 3.1 at Dallas Tech Fest 2011Arun Gupta

OSGi and Java EE: A Hybrid Approach to Enterprise Java Application DevelopmentSanjeeb Sahoo

The document discusses using OSGi and Java EE together for enterprise application development. It provides an overview of OSGi including modules, services, and lifecycle. OSGi allows Java EE applications to be built as bundles that can leverage Java EE services. Specifications integrate technologies like JPA, JTA, and web applications. A demo shows lazy loading with JPA, EJB as a service, and security/transaction context propagation. More advanced topics include CDI injection of OSGi services and demos. The hybrid approach provides modularity, dynamism, and ease of deployment benefits for enterprise applications.

OSGi and Java EE in GlassFish - Tech Days 2010 IndiaArun Gupta

GlassFish v3 supports OSGi bundles and enables hybrid applications that can leverage both OSGi and Java EE. It implements Java EE services and APIs as OSGi services, allowing OSGi bundles to access Java EE functionality. This allows for improved modularity, reusability, and a faster development cycle compared to traditional Java EE applications. Going forward, GlassFish aims to better support OSGi-enabled Java EE applications and improve the underlying OSGi framework administration.

GlassFish OSGi - Java2days 2010Alexis Moussine-Pouchkine

GlassFish provides a modular and extensible Java EE application server runtime based on OSGi. It allows developers to extend GlassFish through OSGi bundles and also supports hybrid applications that are both Java EE archives and OSGi bundles. GlassFish integrates OSGi services like JPA, JMS, and EJB to provide a unified runtime for Java EE and OSGi applications and aims to offer the benefits of modularity, independent lifecycles, and standard application models to Java EE developers.

MySQL Replication Performance in the CloudVitor Oliveira

Smalltalk in Enterprise ApplicationsESUG

The document discusses using Smalltalk in enterprise applications. It provides background on NovaTec GmbH, a German software consulting company, and Andreas Tönne, a managing consultant at NovaTec. It then discusses finding a place for Smalltalk within enterprise architectures and compares classes in Smalltalk in 1995 versus 2010. The document calls for waking up to Smalltalk's potential in the enterprise and integrating it within Java EE architectures. It argues that Java EE is less complex now and provides examples of simple Java EE applications. Finally, it notes that Smalltalk currently spells "Do It Yourself" in the enterprise rather than having standard component and infrastructure models like Java EE.

Gf University 27may09 AmersfoortEugene Bogaart

Singularity Rethinking The Software Stackalanocu

The document describes the Singularity project, which aims to redesign operating system architectures and software stacks to improve dependability and trustworthiness. The key architectural features of Singularity systems are software-isolated processes (SIPs) for isolation, contract-based channels for communication between SIPs, and manifest-based programs (MBPs) for verification of system properties. SIPs provide lightweight process isolation through type safety instead of hardware protection. Communication between SIPs occurs via channels defined by message contracts. MBPs specify the code and behavior of processes.

OpenSSO Roadmap AquariumEduardo Pelegri-Llopart

Using Device Abstraction Layers in OSGi based Embedded Systems - Dimitar Valt...mfrancis

OSGi is gaining popularity as enabling technology for building embedded system in residential, automotive and M2M markets. In all these contexts it is often necessary to communicate with IP and non-IP devices by using various protocols such as Zigbee, ZWave, KNX, UPnP etc. In order to provide a convenient programming model suitable for the realization of end-to-end services it is very useful to define and apply an abstraction layer which unifies the work with the different devices. This presentation summarizes the existing approaches for the realization of a device abstraction layer and comments their advantages and disadvantages. A reference architecture based on the experience gained from numerous real-life projects is presented and explained.

GlassFish 3.1 – Simplifying your Java EE 6 Development and Deployment @ JAX L...Arun Gupta

Java EE 6 Clustering with Glassfish 3.1 Shreedhar Ganapathy

GlassFish Server 3.1 is the first Java EE 6 application server with clustering and high availability capabilities. It was released in February 2011 and provides in-memory replication and clustering. The development of GlassFish is focused on flexibility, extensibility, and developer productivity through features like fast auto-deploy and incremental compiling. It utilizes a modular architecture based on OSGi and has over 260 modules.

Oracle Fusion Middleware - pragmatic approach to build up your applications -...ORACLE USER GROUP ESTONIA

Oracle Fusion Middleware provides a complete set of integrated middleware products and services for building applications. It includes components for web and mobile development, user engagement, content management, business intelligence, identity management, integration, and application development tools. The platform offers high performance, scalability, availability, and security. Oracle Fusion Middleware uses a service-oriented architecture and supports both cloud and on-premises deployments. It allows organizations to modernize applications and integrate legacy systems on a single, open standards-based platform.

Boston 2011 OTN Developer Days - GlassFishArun Gupta

Foundation for optimized data center & private cloudJS Park

The document discusses Oracle's Exalogic Elastic Cloud platform. It highlights challenges with traditional IT environments like fragmentation, inflexibility and high costs. Exalogic is presented as a solution that features engineered hardware and software that are tested, certified, deployed and supported together, improving performance, flexibility and efficiency. Exalogic allows organizations to deploy applications faster, operate more efficiently and grow faster and more predictably.

Resume_GeorgeGeorge lv

This document provides a summary of George Lu's professional experience and qualifications. He has over 9 years of experience in Java development, particularly with banking and financial applications. Some of his skills and achievements include delivering projects successfully, resolving issues like performance and threading, and leading and training offshore teams. He is proficient in technologies like Java, Spring, Hibernate, SQL, and has worked with companies including Moody's Analytics and Credit Suisse.

Structuring software systems with OSGi - Ulf Fildebrandtmfrancis

OSGi is providing a module system, but during implementation in projects it becomes difficult to really use the benefits of an OSGi runtime. Without follow the principles an OSGi system can evolve to a tightly-coupled system like in the past. Some principles and guidelines have to be followed to achieve a good architecture of a software system: - interface/implementation separation for bundles - visibility usage of bundles (import/export) - extensibility for services (and special focus on declarative services) - layering of bundles and using declarative service for layer communication - mocking of layers to achieve maturity of the implementation - interface evolution of bundles to achieve extensibility The presentation will show the changes by refactoring a small web application. The application starts as a tightly coupled system and will be improved by applying the architecture principles. So, in the presentation a lot of coding will be shown, until a good structure of the application is achieved. The guidelines are based on experiences in different projects and are used as best practices in new projects.

GlassFish OSGi ServerArtur Alves

GlassFish Server is the open source application server for Java EE. It provides a proven, high-quality Java EE runtime and is the reference implementation for Java EE standards. GlassFish Server 3.1 combines the benefits of clustering and centralized administration from version 2.1.1 with the modularity and Java EE 6 support of version 3.x. It focuses on developer productivity through tools integration and an improved embedded API, along with updated technologies like Grizzly WebSocket support and refreshed Java EE components.

OSGi enRoute Unveiled - P Kriensmfrancis

OSGi enRoute is an OSGi project to make OSGi as easy to use as some of non-java dynamic web development environments but still provide the benefits of OSGi's strong modularity. OSGi makes it easy to get started with OSGi by providing an integrated tool chain with several runtime environments, that uses OSGi as it always was intended to be used. By leveraging OSGi's powerful features like services and the powerful requirement/capability model, development of applications can be significantly simplified. This presentation will provide an introduction to OSGi, the way it is used in enRoute, and then a demo of how to build an application with enRoute. Bio: Peter Kriens is an independent consultant since 1990.He currently works for the OSGi Alliance and Paremus. During the eighties he developed advanced distributed systems for newspapers based on microcomputers based on, at the time very novel, object oriented technologies. For this experience in Objects he was hired by a number of international companies, including Adobe, Intel, Ericsson, IBM, and many others. During his work at Ericsson Research in 1998 he got involved with the OSGi specification; Later he became the primary editor for these specifications. In 2005 he was awarded the OSGi Fellows title. After taking a sabbatical in 2012 to develop jpm4j he returned to the OSGi Alliance to help increasing adoption. He is Dutch but decided to live in France.

Eclipse Modeling Framework and plain OSGi the easy way - Mark Hoffman (Data I...mfrancis

OSGi Community Event 2018 Presentation by Mark Hoffmann (Data In Motion) Abstract: This talk will show you how the EMF framework can be used in pure OSGi environments other than Equinox. We will introduce you into free configurable ResourceSets and the principle of a ResourceSetFactory. This enables your application to have multiple tenants with different model visibillity. The profit of OSGi services provides a behavior where even models can come and go all the time. We will also give you look inside, how easy it is to extend the default code generation process of EMF to generate OSGi service component that handle the model registration in an OSGi way.

OSGi and Java 9+ - BJ Hargrave (IBM)mfrancis

OSGi Community Event 2018 Presentation by BJ Hargrave (IBM) Abstract: Java 9 introduced the Java Platform Module System (JPMS) as a way to modularize the Java platform and it can be also be used by developers to modularize their own applications, although JPMS lack a number of important features for software running on the Java platform. As people look to support the latest versions of the Java platform, changes introduced in Java 9 related to JPMS led to the needs for some features in the OSGi Core specification. OSGi framework implementations like Eclipse Equinox and Apache Felix and tools like Bnd were updated to support these new features. This session will explore the Java 9+ support added to OSGi Core R7 and Bnd and help you learn how to navigate the world of Java 9+ and OSGi.

More Related Content

Similar to A Fault Tolerance Concept for Distributed OSGi Applications - Fabian Meyer (20)

GlassFish Server 3.1: Deploying your Java EE 6 ApplicationsArun Gupta

Deploying Java EE 6 Apps in a Cluster: GlassFish 3.1 at Dallas Tech Fest 2011Arun Gupta

OSGi and Java EE: A Hybrid Approach to Enterprise Java Application DevelopmentSanjeeb Sahoo

OSGi and Java EE in GlassFish - Tech Days 2010 IndiaArun Gupta

GlassFish OSGi - Java2days 2010Alexis Moussine-Pouchkine

MySQL Replication Performance in the CloudVitor Oliveira

Smalltalk in Enterprise ApplicationsESUG

Gf University 27may09 AmersfoortEugene Bogaart

Singularity Rethinking The Software Stackalanocu

OpenSSO Roadmap AquariumEduardo Pelegri-Llopart

Using Device Abstraction Layers in OSGi based Embedded Systems - Dimitar Valt...mfrancis

GlassFish 3.1 – Simplifying your Java EE 6 Development and Deployment @ JAX L...Arun Gupta

Java EE 6 Clustering with Glassfish 3.1 Shreedhar Ganapathy

Oracle Fusion Middleware - pragmatic approach to build up your applications -...ORACLE USER GROUP ESTONIA

Boston 2011 OTN Developer Days - GlassFishArun Gupta

Foundation for optimized data center & private cloudJS Park

Resume_GeorgeGeorge lv

Structuring software systems with OSGi - Ulf Fildebrandtmfrancis

GlassFish OSGi ServerArtur Alves

OSGi enRoute Unveiled - P Kriensmfrancis

GlassFish Server 3.1: Deploying your Java EE 6 ApplicationsArun Gupta

Deploying Java EE 6 Apps in a Cluster: GlassFish 3.1 at Dallas Tech Fest 2011Arun Gupta

OSGi and Java EE: A Hybrid Approach to Enterprise Java Application DevelopmentSanjeeb Sahoo

OSGi and Java EE in GlassFish - Tech Days 2010 IndiaArun Gupta

GlassFish OSGi - Java2days 2010Alexis Moussine-Pouchkine

MySQL Replication Performance in the CloudVitor Oliveira

Smalltalk in Enterprise ApplicationsESUG

Gf University 27may09 AmersfoortEugene Bogaart

Singularity Rethinking The Software Stackalanocu

OpenSSO Roadmap AquariumEduardo Pelegri-Llopart

Using Device Abstraction Layers in OSGi based Embedded Systems - Dimitar Valt...mfrancis

GlassFish 3.1 – Simplifying your Java EE 6 Development and Deployment @ JAX L...Arun Gupta

Java EE 6 Clustering with Glassfish 3.1 Shreedhar Ganapathy

Oracle Fusion Middleware - pragmatic approach to build up your applications -...ORACLE USER GROUP ESTONIA

Boston 2011 OTN Developer Days - GlassFishArun Gupta

Foundation for optimized data center & private cloudJS Park

Resume_GeorgeGeorge lv

Structuring software systems with OSGi - Ulf Fildebrandtmfrancis

GlassFish OSGi ServerArtur Alves

OSGi enRoute Unveiled - P Kriensmfrancis

More from mfrancis (20)

Eclipse Modeling Framework and plain OSGi the easy way - Mark Hoffman (Data I...mfrancis

OSGi and Java 9+ - BJ Hargrave (IBM)mfrancis

Simplify Web UX Coding using OSGi Modularity Magic - Paul Fraser (A2Z Living)mfrancis

OSGi for the data centre - Connecting OSGi to Kubernetes - Frank Lyaruumfrancis

This document discusses connecting the OSGi framework to Kubernetes for managing applications in container-based environments. It raises questions about building systems that can update while running and whether years spent on this have been wasted. It also briefly mentions a demo of OSGi and Kubernetes integration and asks why a load balancer wouldn't work instead. The document calls for feedback on sessions and ideas about OSGi, Kubernetes, immutable vs mutable systems, and J2EE versus OSGi.

Remote Management and Monitoring of Distributed OSGi Applications - Tim Verbe...mfrancis

OSGi Community Event 2018 Presentation by Tim Verbelen (imec) & Jan S. Rellermeyer (TU Delft) Abstract: With the proliferation of cloud computing and more recently mobile and edge computing, there is a increasing demand to build flexible and robust distributed applications. The OSGi service and module technology is a key enabler for such deployment. Recent additions to the OSGi standards provide a set of services that provide interfaces for managing distributed instances of OSGi frameworks. The REST Service (added in R6 compendium) offers an easy and language-independent way to manage bundes and introspect services from outside the network. The Cluster Information specifications (added in R7 compendium) provide means for applications to manage and monitor the deployment intrinsically, building on top of the Remote Service specifications. In the Eclipse Concierge project, we have provided the reference implementations of both specifications. In this talk, we will show how the services can be used to build distributed applications that benefit from the OSGi modularity.

OSGi with Docker - a powerful way to develop Java systems - Udo Hafermann (So...mfrancis

OSGi Community Event 2018 Presentation by Udo Hafermann (Software AG) Abstract: In this talk we will share our experiences in developing a tool chain from classes, to bundles, to containers, to systems. OSGi and Docker come together in a compelling way where the former provides modularity "in the small" and the latter "modularity in the large". We discover how the unique characteristics of OSGi enable a smooth transition from small to large. The resulting environment enables developers to grow distributed systems on their local machine and test them with plain JUnit at all levels of granularity - classes to systems. During development OSGi enables the tool chain to update the system without container rebuilds. While an increase in productivity is one benefit of such an environment, an arguably more important benefit is the way it empowers developers to gain new insights.

A real world use case with OSGi R7 - Jurgen Albert (Data In Motion Consulting...mfrancis

OSGi Community Event 2018 Presentation by Jurgen Albert (Data In Motion Consulting GmbH) Abstract: OSGi is often conceived as a tool to write efficient Java Applications for resource limited Devices or If resources are a real issue in complex applications. On the other hand Microservices became the buzzword of the cloud and is often implemented using Spring or other Programming languages. OSGi carries the concept of microservices in its core and is therefore much better suited to the task then most other approaches. This talk will show you how a service can be built with a real-worldish use case, leveraging the power of OSGi R7. It will show the combined usage of PushsStreams, the JaxRS Whiteboard, the configurator, remote deployment and a lot of the other cool things OSGi has to offer.

OSGi Feature Model - Where Art Thou - David Bosschaert (Adobe)mfrancis

OSGi Community Event 2018 Presentation by David Bosschaert (Adobe) Abstract: OSGi lends itself well to develop extensible applications assembled from reusable modules, where a set of bundles together with a set of configurations deployed to a provisioned OSGi framework is the application. While this works very well for the originally intended use-cases, maintaining and building large applications developed by multiple teams often requires to assemble multiple larger components for which there is limited support in OSGi as of today. This is especially true in cases where multiple groups of bundles, configuration, metadata, and other artifacts need to be combined. In this talk we will introduce you to OSGi RFP-188, named OSGi Features, which defines the requirements on providing a solution. We'll establish a shared understanding of the problem space and how it relates to already available mechanisms in OSGi (like e.g. subsystems, deploymentadmin, startlevels, etc.) and will subsequently, review it in the context of some of the current (open source) solutions like Apache Karaf Features and Apache Sling Features and Bnd.

Migrating from PDE to Bndtools in Practice - Amit Kumar Mondal (Deutsche Tele...mfrancis

OSGi Community Event 2018 Presentation by Amit Kumar Mondal (Deutsche Telekom AG) & Jochen Hiller (Deutsche Telekom AG) Abstract: QIVICON is an Eclipse SmartHome based solution from Deutsche Telekom AG. It utilises OSGi to provide a modular Java runtime. Since the beginning, QIVICON leveraged Eclipse PDE with Maven & Eclipse Tycho as its build technology but over the time, the complexity increased. It became hard to get an overview and manage the runtime and build dependencies. Especially maintaining target configurations for IDE and CI/CD build, having different embedded gateways for installation increased complexity significantly. Bndtools is the 'swiss army knife' in the context of OSGi development since it takes the nitty-gritty pains and loads off the developer's chest. And that's why we decided to avail the benefits of Bndtools. But, many other OSGi-based projects still cannot avail the benefits as they are very tightly coupled with Eclipse PDE. Want to make a switch from your existing PDE source base to Bndtools? This talk would give you an overview to proceed towards this. We would like to further demonstrate in this talk how to set up a Bndtools workspace from an existing PDE workspace, convert all current projects to Bnd projects and embrace the OSGi-way of developing bundles. Since QIVICON containing more than 350 projects utilised this solution to move to a higher modularity maturity level, this talk would, therefore, outline the pros, cons and the learnings using Bndtools in such a big OSGi project for embedded development.

OSGi CDI Integration Specification - Ray Augé (Liferay)mfrancis

How OSGi drives cross-sector energy management - Jörn Tümmler (SMA Solar Tech...mfrancis

SMA is an energy equipment supplier that was seeking a solution for cross-sector energy management. They evaluated OSGi and decided to develop their own framework based on OSGi. They encountered several problems initially but overcame them by improving API design, avoiding dependencies, and using helper classes. They have now successfully applied OSGi in their products and find that it defines clean module deployment and versioning while supporting dynamic updates.

Improved developer productivity thanks to Maven and OSGi - Lukasz Dywicki (Co...mfrancis

OSGi Community Event 2018 Presentation by Lukasz Dywicki (Code-House) Abstract: During this short presentation I will revisit existing mechanisms and approach towards OSGi and JEE development. I will show how many manual steps can be avoided and how to maintain project in effective manner. I will try to find a balance between execution environment requirements and programmer happines at same time. I believe that OSGi and Eclipse ecosystem experience troubles gaining people from outside for few reasons. Beside overall impression of OSGi complexity there is equally old and invalid complain about quaility of developer tooling. Since invention of BND development experience can be really pleasant and independent of text editor/IDE preferences. Sadly lots of people still rely on former experiences spreading black/bad PR. I would like to clarify their point. After this presentation attendees will learn: How to use Maven to build OSGi projects (without Tycho). How to automate manual tasks. How to build custom software distributions with Maven artifacts and run it with Apache Karaf. That OSGi development doesn't differ much from regular day-to-day usage of application servers or microservice runtimes. This talk is intended for people who know basics of OSGi as it will show few basic technics towards better developer productivity.

It Was Twenty Years Ago Today - Building an OSGi based Smart Home System - Ch...mfrancis

OSGi Community Event 2018 Presentation by Christer Larsson (Makewave) Abstract: OSGi was originally designed for Smart Homes and Residential Gateways almost 20 years ago. This talk will present how the OSGi specifications have evolved over the years, and how you today, in 2018, design an OSGi based Smart Home System. A real world use case of a Swedish Smart Home start-up company will be used to illustrate different design principles and how OSGi remains as relevant today as it was when it started.

Popular patterns revisited on OSGi - Christian Schneider (Adobe)mfrancis

This document discusses how various software design patterns can be applied within the OSGi runtime environment. It describes patterns like Observer/Listener, OSGi Whiteboard, Dependency Injection, Circuit Breaker, and Domain-Driven Design and how they differ or are adapted when used with OSGi. For example, the OSGi Whiteboard pattern allows services and listeners to be loosely coupled without direct dependencies, and OSGi's declarative services specification provides a way to perform dependency injection and manage component lifecycles. The document argues that applying patterns like having microservices per bounded context can help match the original ideas of microservices while minimizing remote communication when using OSGi.

Integrating SLF4J and the new OSGi LogService 1.4 - BJ Hargrave (IBM)mfrancis

OSGi Community Event 2018 Presentation by BJ Hargrave (IBM) Abstract: OSGi Compendium R7 provides a major update to the OSGi LogService specification. A new logging API is added which supports logging levels and dynamic logging administration. A new Push Stream-based means of receiving log entries is also added. But it is quite often the case you need to use other code such as open source projects which are using slf4j for their logging API. This session will explore the new OSGi LogService changes and how you can integrate code using both slf4j logging and OSGi LogService logging.

OSG(a)i: because AI needs a runtime - Tim Verbelen (imec)mfrancis

OSGi Community Event 2018 Presentation by Tim Verbelen (imec) Abstract: Nowadays AI is reaching new heights on the hype cycle, especially due to recent advances in deep learning techniques. A lot of deep learning frameworks exist for creating and training deep neural networks, the most popular ones being PyTorch and TensorFlow. However, how to integrate, deploy and manage these neural networks in complex software systems is often overlooked. In this talk we show how OSGi can be used as a modular runtime for deep learning models. We embed those models inside OSGi bundles, and use the extender pattern to make these available as OSGi services. You can then use your favorite OSGi specs such as DS and PushStreams to integrate these into your application.

Flying to Jupiter with OSGi - Tony Walsh (ESA) & Hristo Indzhov (Telespazio V...mfrancis

OSGi Community Event 2018 Presentation by Tony Walsh (ESA) & Hristo Indzhov (Telespazio Vega) Abstract: The European Space Operations Centre (ESOC) is the main operations center for the European Space Agency (ESA), operating a number of earth observation and scientific missions. Monitoring and control functions needed by spacecraft operators are provided by software systems which are reused across missions, but tailored and extended for mission specific needs. The current generation of monitoring and control systems are becoming obsolete and a European wide initiative called the European Ground Systems Common Core (EGS-CC) (http://www.egscc.esa.int) has been started to develop the next generation. This talk will explain why OSGi was chosen and how it is used in the development of next generation of monitoring and control software. It will describe how OSGi provides the necessary framework that enables the software to be extended for the different space systems it is expected to support. The overall software architecture will be discussed, some of the challenges faced and the benefits gained by using OSGi. The first target mission for the system is JUICE (http://sci.esa.int/juice) which will explore the moons of Jupiter and which is scheduled for launch in 2022.

MicroProfile, OSGi was meant for this - Ray Auge (Liferay)mfrancis

OSGi Community Event 2018 Presentation by Ray Augé (Liferay) Abstract: The craze is fully on. The past couple of years have seem micro services grow from next _flava_ to fully consuming of the software industry. The Eclipse micorprofile.io project is tackling the issue putting common usage patterns together over a foundation of CDI. What better assembly driver is there than OSGi to put it all together. This talk will demonstrate building your own MicroProfile using OSGi and the OSGi enRoute packaging model.

Prototyping IoT systems with a hybrid OSGi & Node-RED platform - Bruce Jackso...mfrancis

OSGi Community Event 2018 Presentation by Bruce Jackson (Myriad) Abstract: Node-RED is often used as a protyping tool for IoT systems. However, there are also a large number of OSGi components that have already been built to interface to devices, sensors and systems. In this talk I will show how two completely different runtime environments (OSGi and Node-RED) can be combined into a single platform for prototyping (and more) combining the strengths of both languages and systems. Being able to quickly and simply prototype IoT application is extremely useful, and to this end many people have adopted Node-Red, a Node.js based runtime with extensive support for plugins to interface to various IoT hardware and protocols. However, this requires these services/protocols to be developed in Javascript, and there is already a significant body of code developed in Java/OSGi that it would be desirable to re-use. The talk will explain how it is possible to: Create and manage a Node-Red runtime from within an OSGi bundle  Share OSGi components and object into the Node-Red runtime  Interact and build Node-Red flows that exchange data and call methods between Node.js and OSGi This is obviously useful for the original purpose: prototyping IoT systems, but also demonstrates some interesting techniques for bridging between different languages and runtimes.

How to connect your OSGi application - Dirk Fauth (Bosch)mfrancis

OSGi Community Event 2018 Presentation by Dirk Fauth (Bosch) Abstract: In todays connected world the requirement to connect applications across network boundaries has become a common requirement. With OSGi there are several ways to accomplish this, as there are different specifications to achieve this. In this talk we will look at some of these specifications to show what options there are and which might fit your requirements. Starting from an architecture that makes use of the HTTP Whiteboard pattern, over Remote Services to finally showing the usage of the JAX-RS Whiteboard specification introduced with R7. We will show the general usage of these specifications and explaining the advantages and disadvantages of each solution.