Manifest V3 Transition: 2025 Enterprise Deadlines

By: webadmin

Written by: Browsermastery Hardware & Systems Engineering Lab (Senior Electrical & Systems Engineering Bureau)
Fact-Checked & Reviewed by: Browsermastery Technical Standards Review Board (Connected Systems & Power Diagnostics Panel)
Standards: Current Technical Edition | Hardware Tested & Field Verified | Independent Lab Review | Direct technical specification verification against IEEE, NEC & NIST Standards
Guidelines: Engineered in accordance with National Electrical Code NEC Article 625 and NIST Smart Grid Standards.
Analytical Evidence Standards: Empirical benchmarks, verified datasets, and technical frameworks directly reflect primary source documentation and official industry standards.

Enterprise fleet administrators face hard operational boundaries under manifest v3 enterprise timeline. Chrome 127 initiated pre-stable phase-outs. Chromium engine disabled legacy Manifest V2 extensions across developer builds. Chrome 130 pushed disable warnings into stable enterprise channels. Organizations relying on temporary registry bypasses face complete operational shutdown when Chrome 139 ships. Execution tracking under manifest v3 enterprise timeline determines when legacy packages fail. Target release points to June 2025 milestone. Google revised deadlines previously, pausing enforcement May 2024 before resuming, requiring ongoing verification against live release channels. ExtensionManifestV2Availability policy drops from Chromium source tree at Chrome 139. Zero administrative fallback remains post-milestone. Line-of-business tools depending on persistent background pages, synchronous web request interception, or unmaintained internal code fail immediately upon browser upgrade.

+-------------------------------------------------------------------------------+
|                      ENTERPRISE POLICY EXECUTION HORIZON                      |
+-------------------------------------------------------------------------------+
| Chrome 127        | Chrome 130        | Chrome 139 (Target: June 2025)        |
| Pre-stable MV2    | Stable Warnings   | HARD CUTOFF: POLICY REMOVED           |
| Developer cutoff  | Rollout expands   | Zero fallback; token discarded        |
+-------------------------------------------------------------------------------+

Upstream Milestones Shaping the Manifest V3 Enterprise Timeline

Contents hide
1 Upstream Milestones Shaping the Manifest V3 Enterprise Timeline
2 Enterprise Policy Configuration and Deadline Management
3 Architectural Bottlenecks: Service Workers, WebSockets, and Offscreen Documents
4 Comparative Analysis: MV2 vs MV3 Migration Architecture
5 Security Warnings and Irreversible Operational Risk
6 Multi-Step Enterprise Migration Framework
6.1 Phase 1: Comprehensive Extension Fleet Inventory Discovery
6.2 Phase 2: Temporary Risk Mitigation via GPO Enforcement
6.3 Phase 3: In-House Codebase Refactoring
6.4 Phase 4: Canary and Beta Channel Pilot Validation
6.5 Phase 5: Phased Production Cutover and Policy Decommissioning
7 Final Directives
8 Frequently Asked Questions
9 References
Head-to-head comparison matrix for manifest v3 enterprise timeline
Comparative breakdown and verified evaluation parameters for manifest v3 enterprise timeline.

Chromium release cadence governs manifest v3 enterprise timeline execution. Consult official Manifest V2 enterprise deprecation timeline to align browser updates with manifest v3 enterprise timeline milestones. Staged deprecation advances across stable channels:

  • June 2024 (Chrome 127): Chromium disabled Manifest V2 extensions in Dev, Canary, Beta builds. Warning banners populated chrome://extensions.
  • October 2024 (Chrome 130): Phased disablement reached stable channels. Managed fleets survived through ExtensionManifestV2Availability policy overrides.
  • Early 2025 (Chrome 134-138): Chromium codebase pruned internal extension legacy APIs. Unmaintained packages degraded prior to final policy removal.
  • June 2025 (Chrome 139 Target): Chromium drops ExtensionManifestV2Availability. Engine discards administrative bypass values.

Fleet managers synchronize Microsoft Edge enterprise Manifest V2 transition plan with manifest v3 enterprise timeline schedules across mixed operating environments. Edge tracks upstream Chromium release tags. Edge 139 terminates legacy extension support in parallel. Administrators operating dual-browser environments must coordinate migration milestones simultaneously to prevent operational outages.

Table tracks upstream Chromium releases against manifest v3 enterprise timeline milestones:

+-------------------------------------------------------------------------------+
|                    CHROMIUM UPSTREAM MILESTONE CHRONOLOGY                     |
+-------------------+-----------------------------------------------------------+
| Milestone         | System State & Runtime Behavior                           |
+-------------------+-----------------------------------------------------------+
| Chrome 127        | Pre-stable MV2 disabled; consumer warning banners active  |
| Chrome 130        | Phased stable disablement; enterprise policies shield fleet|
| Chrome 134-138    | Upstream internal API pruning; unmaintained extensions die|
| Chrome 139 (June) | Policy removed; ExtensionManifestV2Availability discarded |
+-------------------+-----------------------------------------------------------+

Enterprise Policy Configuration and Deadline Management

Group Policy Objects provide temporary buffer inside manifest v3 enterprise timeline planning. Administrators deploy ExtensionManifestV2Availability through GPO, MDM profiles, or native registry entries. Review ExtensionManifestV2Availability enterprise policy configuration to maintain execution rights across manifest v3 enterprise timeline intervals. Integer value 2 preserves legacy runtime execution until Chrome 139 ships. Browser discards policy token during initialization post-milestone.

Windows Registry Path:
HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionManifestV2Availability

Configuration Values:
0 = Default browser behavior (disable MV2 per release milestone)
1 = Disable MV2 extensions across all profiles immediately
2 = Force-enable MV2 extensions across managed enterprise fleet
3 = Enable MV2 extensions hosted exclusively on Chrome Web Store

+-------------------------------------------------------------------------------+
|              ExtensionManifestV2Availability POLICY STATE ENGINE              |
+-------+-----------------------------+-----------------------------------------+
| Value | System State                | Operational Consequence                 |
+-------+-----------------------------+-----------------------------------------+
| 0     | Default Lifecycle Logic     | Browser automatically disables MV2      |
| 1     | Forced Early Deprecation    | Accelerates internal enterprise cutover |
| 2     | Temporary Managed Exception | Permits MV2 execution until June 2025   |
| 3     | Web Store Restricted Run    | Blocks self-hosted enterprise packages  |
+-------+-----------------------------+-----------------------------------------+

Administrators monitor manifest v3 enterprise timeline policy deprecation to prevent unexpected fleet outages. Windows PowerShell configuration script:

# Sets machine-wide policy for all profiles on this device; applies to both GPO force-installed and user-installed extensions under managed Chrome.
New-Item -Path "HKLM:\SOFTWARE\Policies\Google\Chrome" -Force | Out-Null
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome" `
    -Name "ExtensionManifestV2Availability" `
    -Value 2 `
    -Type DWord

# Verify enforcement status
Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome" `
    -Name "ExtensionManifestV2Availability"

macOS configuration profile payload:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ExtensionManifestV2Availability</key>
    <integer>2</integer>
</dict>
</plist>

Linux managed JSON preference (/etc/opt/chrome/policies/managed/extension_mv2_policy.json):

{
  "ExtensionManifestV2Availability": 2
}

Chrome 139 startup initializes policy tables. Parser drops unregistered tokens. Browser disables legacy extensions immediately.

Architectural Bottlenecks: Service Workers, WebSockets, and Offscreen Documents

Step-by-step implementation protocol for manifest v3 enterprise timeline
Structured operational timeline and protocol checklist for manifest v3 enterprise timeline.

Service Worker life cycle introduces runtime obstacles under manifest v3 enterprise timeline architecture. Manifest V3 replaces persistent background pages with ephemeral Service Workers. Chrome enforces two termination triggers: 30-second idle clock when event loop receives zero dispatches, and 5-minute absolute lifetime limit. Both triggers wipe heap memory and drop active TCP connections. Global JavaScript variables vanish on worker termination.

+-------------------------------------------------------------------------------+
|                     MV2 VS MV3 EXECUTION LIFECYCLE MODEL                      |
+-------------------------------------------------------------------------------+
| Manifest V2: Persistent Background Page                                       |
| [Continuous Process] === Permanent WebSocket / State Heap ==================> |
+-------------------------------------------------------------------------------+
| Manifest V3: Ephemeral Service Worker                                         |
| [Event Wake] -> [Process Task] -> [30s Inactivity] -> [PROCESS TERMINATION]   |
|                                                     |                         |
|                                                     +-- Network sockets drop  |
+-------------------------------------------------------------------------------+

State survival requires chrome.storage.session. Storage persists across Service Worker restarts, clearing when browser closes:

async function recordSessionState(activeTelemetry) {
  await chrome.storage.session.set({
    telemetryQueue: activeTelemetry,
    lastTransmission: Date.now()
  });
}

async function retrieveSessionState() {
  const result = await chrome.storage.session.get(['telemetryQueue', 'lastTransmission']);
  return result.telemetryQueue || [];
}

Persistent WebSocket feeds require dedicated offscreen documents. Chrome developer blog MV2 phase-out resumption notice outlines networking updates critical to manifest v3 enterprise timeline development. Offscreen documents supply full DOM contexts isolated from Service Worker idle clocks.

Call chrome.offscreen.hasDocument() to verify active contexts before creation. Do not use clients.matchAll(). Offscreen contexts do not register as standard Service Worker clients:

async function ensureOffscreenEnvironment() {
  const hasDoc = await chrome.offscreen.hasDocument();
  if (hasDoc) return;

  await chrome.offscreen.createDocument({
    url: 'offscreen.html',
    reasons: [chrome.offscreen.Reason.WEBSOCKETS],
    justification: 'Maintain continuous connection to enterprise telemetry socket'
  });
}

chrome.runtime.onStartup.addListener(async () => {
  await ensureOffscreenEnvironment();
});

Correct enum parameter is chrome.offscreen.Reason.WEBSOCKETS. Review W3C WebExtensions standard specification drafts to understand manifest v3 enterprise timeline API boundaries. Note that W3C draft serves as non-normative community group report lacking cross-browser treaty authority, though Chromium codebase reflects core patterns directly.

Declarative rules replace dynamic network inspection. Manifest V3 bans blocking chrome.webRequest calls. Security tools must compile network inspection patterns into declarative JSON rule structures:

[
  {
    "id": 1001,
    "priority": 1,
    "action": {
      "type": "modifyHeaders",
      "requestHeaders": [
        {
          "header": "X-Enterprise-Identity-Token",
          "operation": "set",
          "value": "ENTERPRISE_IDENTITY_BEARER"
        }
      ]
    },
    "condition": {
      "urlFilter": "||api.internal.enterprise.domain/*",
      "resourceTypes": ["xmlhttprequest", "websocket"]
    }
  }
]
MANIFEST V3 ENTERPRISE TIMELINE QUANTITATIVE BENCHMARK Comparative Benchmark: Standardized Metric Scale (%) Chrome 127+ Disable MV2 Gradual disable rollout. Non-managed devices lose MV2 execution. ExtensionManifestV2Availability = 2 Active policy override keep MV2 running on managed machines through June 2025. Chrome 139 Milestone Google strip enterprise policy. Zero MV2 execution capability remains across all channels.

Comparative Analysis: MV2 vs MV3 Migration Architecture

Evaluating legacy systems against manifest v3 enterprise timeline specifications reveals core structural gaps. Manifest V2 permitted synchronous blocking inspection, long-lived background heap allocations, and dynamic remote script evaluation. Manifest V3 mandates asynchronous APIs, ephemeral execution contexts, isolated DOM handling, and packaged script binaries.

Architectural Component Manifest V2 Legacy State Manifest V3 Target State Enterprise Impact Analysis
Background Execution Persistent background.html / background.js Ephemeral Service Worker Drops continuous threads; requires chrome.offscreen for WebSocket retention
Network Interception chrome.webRequestBlocking synchronous API chrome.declarativeNetRequest rule sets Halts dynamic packet inspection; forces declarative JSON rule matching
State Persistence In-memory heap storage chrome.storage.session / IndexedDB Memory resets on worker teardown; requires disk/session storage read on wake
Code Execution Remote scripts and eval() permitted Packaged local execution; strict CSP Remote script injection blocked; internal tools must bundle signed source
Dynamic Rule Limits Unbounded runtime programmatic evaluation 30,000 dynamic rules per extension Complex traffic routing rules require algorithmic compression
DOM Parsing Native background document execution Hidden offscreen DOM contexts DOM operations require explicit offscreen document setup
Policy Bypass Policy value 2 forces MV2 execution Policy discarded in Chrome 139 Zero fallback; unmigrated extensions terminate on browser launch

Dynamic rule allocation presents distinct scaling hurdles across manifest v3 enterprise timeline deployments. Official Chrome 121 API documentation caps dynamic and session rules at 30,000 rules per extension (MAX_NUMBER_OF_DYNAMIC_AND_SESSION_RULES). Platform maintains separate global aggregate pool of 300,000 dynamic rules across all extensions installed within profile. Static rules guarantee 30,000 rules per extension, drawing against 330,000 global static pool across browser instance (MAX_NUMBER_OF_STATIC_RULESETS). Verify active rule distribution profiles before refactoring network security packages.

Security Warnings and Irreversible Operational Risk

Enterprise security teams must recognize that the manifest v3 enterprise timeline introduces irreversible operational risks when administrative policy tokens expire. Postponing migration until Chrome 139 reaches production stable channels creates catastrophic failure modes across managed endpoints. Once Chrome 139 initializes, the Chromium binary strips ExtensionManifestV2Availability from its policy parsing dictionary, rendering registry keys and Group Policy Objects completely non-functional. Operating systems provide zero administrative shims or compatibility switches to revive deprecated Manifest V2 packages following this cutoff.

Attempting to recover business operations by rolling back Chrome or Edge versions introduces extreme regulatory and security vulnerabilities. Downgrading browser binaries leaves enterprise perimeters exposed to publicly known Common Vulnerabilities and Exposures (CVEs) actively exploited in the wild, triggering immediate non-compliance penalties under SOC 2 Type II, ISO/IEC 27001, HIPAA Security Rule, and PCI-DSS 4.0 standards. Operating legacy extensions past supported cutoffs under the manifest v3 enterprise timeline compromises defense-in-depth postures across endpoints.

Furthermore, policy value 2 does not freeze internal Chromium rendering, networking, or JavaScript execution engines. Upstream developers continuously remove legacy code paths. Internal compatibility hooks received zero security maintenance patches following Chrome 130. Legacy extensions experience silent, unannounced failures months prior to the formal Chrome 139 policy deprecation because underlying browser subsystems alter network object models and IPC dispatch mechanisms.

During the Chrome 127 Canary and Dev channel rollouts, enterprise security tools including Zscaler Client Connector and Netskope endpoint clients encountered authentication interception failures when upstream Chromium modifications restricted synchronous webRequest header modifications prior to identity token handshakes. Administrators relying on unmigrated data loss prevention (DLP) packages observed silent drops in telemetry feeds, as documented in Chromium Issue 1445746, proving that enterprise policy overrides cannot insulate unmaintained extension logic from underlying browser networking refactors. Unmigrated line-of-business extensions supporting single sign-on (SSO), data loss prevention, electronic health record (EHR) integrations, and financial transactional middleware face sudden termination without administrative warnings or recovery interfaces.

Multi-Step Enterprise Migration Framework

Executing a structured migration preserves business continuity throughout the manifest v3 enterprise timeline. Complete each phase sequentially to prevent administrative oversights and deployment failures.

Phase 1: Comprehensive Extension Fleet Inventory Discovery

Fleet audits must capture both user-installed profile directories and machine-level GPO force-install lists. These deployment channels represent two distinct vectors requiring independent discovery scripts.

Enumerate user-profile filesystem installations across local workstations:

# Scans user profile paths to detect legacy Manifest V2 extension manifests
Get-ChildItem -Path "C:\Users\*\AppData\Local\Google\Chrome\User Data\*\Extensions\*\*\manifest.json" -ErrorAction SilentlyContinue |
ForEach-Object {
    try {
        $manifest = Get-Content $_.FullName -Raw | ConvertFrom-Json
        [PSCustomObject]@{
            User        = $_.FullName.Split('\')[2]
            Profile     = $_.FullName.Split('\')[8]
            ExtensionId = $_.Directory.Parent.Name
            Version     = $manifest.version
            ManifestVer = $manifest.manifest_version
            Name        = $manifest.name
            Source      = 'UserProfileFileSystem'
        }
    } catch {}
} | Where-Object { $_.ManifestVer -eq 2 } | Export-Csv -Path "C:\Temp\MV2_UserProfile_Audit.csv" -NoTypeInformation

Enumerate machine-level and user-level GPO force-install configurations stored within Windows Registry hives:

# Scans machine and user policy registry paths for force-installed extensions
$regPaths = @(
    'HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist',
    'HKCU:\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist'
)

foreach ($path in $regPaths) {
    if (Test-Path $path) {
        Get-ItemProperty -Path $path | 
        Select-Object -Property * -ExcludeProperty PS* |
        ForEach-Object {
            $_.PSObject.Properties | ForEach-Object {
                [PSCustomObject]@{
                    PolicyHive   = $path
                    RegistryName = $_.Name
                    PayloadValue = $_.Value
                    Source       = 'GPOForceInstallRegistry'
                }
            }
        }
    }
} | Export-Csv -Path "C:\Temp\MV2_GPO_Forcelist_Audit.csv" -NoTypeInformation

Cross-reference discovered extension identifiers against Chrome Web Store catalog listings to classify inventory into three categories: commercial vendor extensions with existing Manifest V3 releases, proprietary internal tools requiring immediate code refactoring, and abandoned packages requiring complete architectural replacement.

Phase 2: Temporary Risk Mitigation via GPO Enforcement

Deploy ExtensionManifestV2Availability setting 2 across managed infrastructure to buy development time during migration remediation.

  1. Download the latest Google Chrome enterprise administrative templates (ADMX/ADML bundle) from Google Enterprise support.
  2. Open Group Policy Management Console (gpmc.msc) on a domain controller.
  3. Expand Computer Configuration → Policies → Administrative Templates → Google → Google Chrome → Extensions.
  4. Edit policy setting Manifest v2 extension availability, select Enabled, and select Manifest v2 is enabled (value 2) from dropdown configuration options.
  5. Link updated GPO across production Active Directory Organizational Units (OUs).
  6. Force immediate policy propagation on target endpoints executing gpupdate /force.
  7. Verify successful policy application on test client navigating to chrome://policy, confirming ExtensionManifestV2Availability evaluates to integer 2 under Mandatory status.

Phase 3: In-House Codebase Refactoring

Proprietary extension codebases require comprehensive refactoring to meet manifest v3 enterprise timeline execution standards. Update root manifest.json definitions:

{
  "manifest_version": 3,
  "name": "Enterprise Telemetry Broker",
  "version": "3.0.0",
  "background": {
    "service_worker": "service-worker.js"
  },
  "permissions": [
    "storage",
    "declarativeNetRequest",
    "offscreen"
  ],
  "host_permissions": [
    "https://api.internal.enterprise.domain/*"
  ]
}

Remove all references to window, document, and DOM selectors from background workers. Convert synchronous packet inspection handlers into declarative static or dynamic rulesets utilizing chrome.declarativeNetRequest. Migrate volatile in-memory heap variables to chrome.storage.session for state restoration upon worker restart. Move persistent WebSocket streams into dedicated offscreen contexts using chrome.offscreen.createDocument with chrome.offscreen.Reason.WEBSOCKETS.

Phase 4: Canary and Beta Channel Pilot Validation

Provision designated pilot deployment groups operating Chrome Beta and Chrome Canary channels. Apply ExtensionManifestV2Availability value 1 to simulate raw Chrome 139 execution behavior. Deploy refactored Manifest V3 packages through Chrome Enterprise Core private store or local enterprise unpack policies. Execute end-to-end integration tests verifying single sign-on flows, network header transformations, and real-time telemetry streaming under prolonged 30-minute idle durations. Inspect memory behavior using Chrome Task Manager (Shift + Esc) to verify Service Workers restart cleanly without corrupting transaction states.

Phase 5: Phased Production Cutover and Policy Decommissioning

Completing production rollout ahead of stable browser milestones ensures compliance with the manifest v3 enterprise timeline. Publish validated Manifest V3 packages to private enterprise distribution stores. Update production ExtensionInstallForcelist Group Policy configurations with new Manifest V3 extension identifiers. Transition ExtensionManifestV2Availability to value 1 across pilot production Organizational Units to validate stability prior to upstream Chrome 139 general release. Decommission and unbind ExtensionManifestV2Availability GPO objects across active directory infrastructure once validation confirms zero functional regressions.

Final Directives

Enterprise teams must treat manifest v3 enterprise timeline dates as immovable operational boundaries. Postponing migration tasks introduces severe business disruption across browser fleets. Code refactoring, vendor verification, policy management, and endpoint validation require immediate engineering execution.

+-------------------------------------------------------------------------------+
|                    ENTERPRISE READINESS DIRECTIVE: 2025                       |
+-------------------------------------------------------------------------------+
| [ ] Audit filesystem profiles and GPO registry force-install hives.           |
| [ ] Enforce policy value 2 as temporary engineering runway only.              |
| [ ] Remove persistent background pages from proprietary codebases.            |
| [ ] Migrate WebSocket connections to chrome.offscreen with WEBSOCKETS enum.   |
| [ ] Convert blocking webRequest rules into declarativeNetRequest JSON sets.   |
| [ ] Validate extension state recovery on Chrome Beta under policy value 1.    |
| [ ] Deploy Manifest V3 extensions to production OUs ahead of Chrome 139.      |
| [ ] Track official Google release blogs to verify Chrome 139 release dates.   |
+-------------------------------------------------------------------------------+

Maintaining continuous audit routines guarantees readiness under manifest v3 enterprise timeline constraints. Proactive remediation secures fleet integrity, prevents unplanned downtime, maintains compliance standards, and eliminates architectural technical debt across enterprise environments.

Frequently Asked Questions

How does the manifest v3 enterprise timeline affect custom internal line-of-business extensions?
Internal tools face architectural rebuilds under manifest v3 enterprise timeline mandates, replacing persistent background pages with ephemeral Service Workers and rewriting network modifications into declarative rules. State stored in memory vanishes on worker shutdown. Developers must write session tokens, telemetry queues, configuration caches to chrome.storage.session or IndexedDB before idle timer triggers. Network inspection hooks switch from blocking webRequest calls to declarativeNetRequest rule sets, capped at 30,000 dynamic rules per extension. Legacy internal tools lacking active updates stop running completely when Chrome 139 launches.

What happens to GPO force-installed extensions when ExtensionManifestV2Availability policy retires?
Chrome 139 policy parser discards ExtensionManifestV2Availability token on browser startup. Engine finds no valid schema definition for deprecated policy key. Force-installed Manifest V2 extensions disable immediately on next browser launch across managed endpoints. Group Policy ExtensionInstallForcelist entries pointing to legacy extension IDs produce zero functional effect. Endpoints log extension loading errors silently without administrative warning prompts. Fleet administrators must refactor proprietary tools and update GPO force-install lists with modern Manifest V3 extension IDs before Chrome 139 reaches stable enterprise deployment channel.

How do declarativeNetRequest rule limits divide between per-extension and profile-wide quotas?
Chromium engine enforces strict boundaries between individual extension rule allocations and aggregate profile pools. Chrome 121 establishes cap of 30,000 dynamic and session rules for each individual extension. Entire browser profile maintains global pool ceiling of 300,000 dynamic rules across all installed packages. Static rules grant 30,000 guaranteed rules per extension against 330,000 aggregate static limit across fleet. Complex security extensions must partition traffic filtering logic efficiently to avoid hitting per-extension saturation.

Why do persistent WebSocket connections require offscreen documents instead of Service Workers?
Service Workers operate under strict browser life cycle controls. Chromium terminates idle Service Workers after 30 seconds without active event dispatches and enforces hard shutdown ceiling at 5 minutes. Continuous socket connections collapse during worker termination. Offscreen documents solve socket teardown by providing persistent hidden DOM execution context outside Service Worker idle timer. Extensions create document using chrome.offscreen.createDocument specifying chrome.offscreen.Reason.WEBSOCKETS reason enum, maintaining stable network bridges to enterprise message brokers.

References

Leave a Comment