Overview

JetPatch 5.0 introduces a significant architectural change, transitioning from a monolithic application to a containerized microservices-based platform.

This change is mostly internal and not reflected in the user interface, but it directly impacts how the system behaves, scales, and is maintained.

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
  • If a single service fails, the rest of the platform continues to operate
• Better performance under load
  • Patch operations and agent workflows are handled more efficiently, especially in large environments
• Faster and safer updates
  • Services can be updated independently without requiring a full system upgrade
• Scalability
  • Worker services can be scaled horizontally based on workload

What Changed

• The platform is no longer delivered as a single RPM-based application
• JetPatch is now composed of multiple containerized services
• Each service has a dedicated role (management, workers, messaging, storage, etc.)
• Services communicate via APIs and messaging mechanisms
• Deployment and orchestration are handled using Docker Compose
• Core components such as PostgreSQL, artifact storage, and messaging are separated and managed independently

How it Works

• Management Service – Handles UI, APIs, and user interactions
• Worker Service – Executes background jobs such as patching and agent operations
• Task Dispatcher – Distributes tasks between services
• Configuration Service – Centralizes configuration and distributes it to services
• Message Broker – Enables communication between services
• Artifact & Patch Repository – Stores agents, connectors, and patch content
• Certificate Store – Manages certificates and trust between services
• Observability Services – Collect logs and metrics for monitoring and troubleshooting

When You May Notice the Change

• During large patch deployments or high system load
• When restarting services (services start independently, not as a single unit)
• During upgrades (faster and more controlled process)
• When reviewing logs (logs are now distributed across services)

What to Expect After Upgrade

• Services may start gradually rather than all at once
• System behavior may appear more asynchronous compared to previous versions
• Logs and troubleshooting require checking multiple services instead of a single log source
• Restarting a specific service does not require restarting the entire platform

Why It Matters

This new architecture provides a more stable and flexible foundation for JetPatch, enabling:

• Easier scaling as environments grow
• Improved fault isolation
• More predictable and lower-impact upgrades
• A foundation for future capabilities such as multi-tenancy and SaaS deployments

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