Red Hat Developer Hub 1.4

Introduction to plugins

Red Hat Customer Content Services

Legal Notice

Abstract

The Red Hat Developer Hub (RHDH) application offers a unified platform with various plugins. Using the plugin ecosystem within the Developer Hub application, you can access your development infrastructure and software development tools.

1. Plugins in Red Hat Developer Hub
1.1. Dynamic plugins in Red Hat Developer Hub
1.2. Comparing dynamic plugins to static plugins

1. Plugins in Red Hat Developer Hub

The Red Hat Developer Hub (RHDH) application offers a unified platform with various plugins. Using the plugin ecosystem within the RHDH application, you can access any kind of development infrastructure or software development tool.

Plugins are modular extensions for RHDH that extend functionality, streamline development workflows, and improve the developer experience. You can add and configure plugins in RHDH to access various software development tools.

Each plugin is designed as a self-contained application and can incorporate any type of content. The plugins utilize a shared set of platform APIs and reusable UI components. Plugins can also retrieve data from external sources through APIs or by relying on external modules to perform the tasks.

RHDH provides both static and dynamic plugins that enhance its functionality. Static plugins are integrated into the core of the RHDH application, while dynamic plugins can be sideloaded into your Developer Hub instance without the need to recompile your code or rebuild the container.

To install or update a static plugin you must update your RHDH application source code and rebuild the application and container image.

To install or update a dynamic plugin, you must restart your RHDH application source code after installing the plugin.

You can also import your own custom-built or third-party plugins or create new features using dynamic plugins.

Dynamic plugins boost modularity and scalability by enabling more flexible and efficient functionality loading, significantly enhancing the developer experience and customization of your RHDH instance.

1.1. Dynamic plugins in Red Hat Developer Hub

You can use RHDH dynamic plugins in environments where flexibility, scalability, and customization are key. Using dynamic plugins in RHDH provides:

Modularity and extensibility: You can add or modify features without altering the core RHDH application. This modular approach makes it easier to extend functionality as needs evolve.
Customization: You can tailor RHDH to fit specific workflows and use cases, enhancing the overall user experience.
Reduced maintenance and update overhead: You can deploy the updates or new features independently of the main RHDH codebase, reducing the risks and efforts associated with maintaining and updating the platform.
Faster iteration: You can create and test new features more rapidly as plugins, encouraging experimentation and enabling you to quickly iterate based on feedback.
Improved collaboration: You can share plugins across teams or even externally. This sharing can foster collaboration and reduce duplication of effort, as well as help establish best practices across an organization.
Scalability: As organizations grow, their needs become complex. Dynamic plugins enable RHDH to scale alongside such complex needs, accommodating an increasing number of users and services.
Ecosystem growth: Fostering the development of plugins can create a dynamic ecosystem around RHDH. This community can contribute to plugins that cater to different needs, thereby enhancing the platform.
Security and compliance: You can develop plugins with specific security and compliance requirements in mind, ensuring that RHDH installations meet the necessary standards without compromising the core application.

Overall, the use of dynamic plugins in RHDH promotes a flexible, adaptable, and sustainable approach to managing and scaling development infrastructure.

1.2. Comparing dynamic plugins to static plugins

Static plugins are built into the core of the RHDH application. Installing or updating a static plugin requires a restart of the application after installing the plugin.

The following table provides a comparison between static and dynamic plugins in RHDH.

Feature	Static plugins	Dynamic plugins
Integration	Built into the core application.	Loaded at runtime, separate from the core.
Flexibility	Requires core changes to add or update features.	Add or update features without core changes.
Development speed	Slower, requires a complete rebuild for new features.	Faster, deploy new functionalities quickly.
Customization	Limited to predefined options.	Easy to tailor platform by loading specific plugins.
Maintenance	More complex due to tightly coupled features.	Enhanced by modular architecture.
Resource use	All features loaded at startup.	Only necessary plugins loaded dynamically.
Innovation	Slower experimentation due to rebuild cycles.	Quick experimentation with new plugins.

Legal Notice

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux® is the registered trademark of Linus Torvalds in the United States and other countries.

Java® is a registered trademark of Oracle and/or its affiliates.

XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.

MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.

Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.