JetPatch 5.0 Overview

Introduction

JetPatch 5.0 introduces a modernized internal architecture, transitioning from a monolithic design to a microservices-based model.
Although these changes occur mainly at the infrastructure level and are not visible in the user interface, they significantly improve how the platform operates behind the scenes — resulting in greater stability, better performance, and more efficient scalability.

Customers may experience smoother operation and more consistent system behavior, especially during intensive patching tasks, agent operations, and other workload-heavy activities.
The updated architecture also supports a more efficient and predictable update process, allowing fixes and enhancements to be introduced with reduced service impact and more manageable release cycles.

JetPatch 5.0 provides a more resilient and flexible foundation that can better accommodate varying workloads and evolving organizational needs.
These improvements deliver a stable, adaptable, and future-ready platform suitable for a wide range of deployment environments.

What does this mean for you as a customer?

• Improved reliability: issues in one service are less likely to affect the entire platform.

  Better performance under load: operations, such as patch processing and agent workflows, run more smoothly.

• Faster, safer updates: smaller components can be upgraded independently with minimal disruption.

• Future-ready architecture: enabling quicker delivery of new capabilities and ongoing enhancements.

What Changed

JetPatch 5.0 replaces the monolithic, RPM-based application with a containerized microservices platform, where each service has a focused role and communicates over APIs and messaging deployed and orchestrated with Docker Compose, delivering better scalability, fault isolation, and upgrade flexibility.

How it Works

• Containers run the platform services

• Compose orchestrates startup, configuration, and dependencies

• PostgreSQL and storage are operated as distinct components

• Certificates and configuration are managed centrally, consumed by services at start-up

Services Overview

Management

• Management service, UI, and APIs

• Worker service, background jobs, patch, and agent jobs

• Task dispatcher

Platform

• Configuration service and central settings distribution

• Message broker 

Content and security

• Certificate store, service certificates, and trust material

• Artifact store, agen,t, and connector packages

• Patch repository, patch content storage, and delivery

Observability

• Log service, centralized log collection, and forwarding

• Metrics service, performance, and health telemetry

Why it Matters

• Scalability: add worker containers as load grows

• Resilience: isolate faults to a single service

• Flexibility: smaller updates, faster rollbacks, simpler refresh

• Readiness: foundation for multi-tenancy and SaaS