dotCMS / dotCMS/core

feat(queue): add cloud-agnostic queue publisher abstraction

Open
#35,630 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Summary

Introduce a DotQueuePublisher interface as a cloud-agnostic queue abstraction for dotCMS. This provides the infrastructure layer for publishing analytics events (and future use cases) to external message queues.

Scope

  • DotQueuePublisher interface with publish() and isAvailable(queueName)
  • DotQueuePublisherLocator for config-driven provider selection (DOT_QUEUE_PROVIDER)
  • SqsQueuePublisher — AWS SQS implementation using IAM/default credentials chain
  • NoOpQueuePublisher — default no-op for environments without queue infrastructure
  • Support for custom providers via fully-qualified class name in config

Parent Epic

Part of #35048

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading parent epic #35048 and the requested DotQueuePublisher, DotQueuePublisherLocator, SqsQueuePublisher, and NoOpQueuePublisher responsibilities. Done means the abstraction, configuration-based provider selection through DOT_QUEUE_PROVIDER, AWS SQS implementation, default no-op behavior, and fully qualified custom-provider support are defined and integrated.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.