Skip to content

Remove or refactor fhir-replication-api #134

Closed
@lmsurpre

Description

@lmsurpre

fhir-replication-api defines an API for "replication events" that can be used to broadcast create/update/delete interactions to a messaging/event engine (e.g. Kafka).
To assist with reliable delivery of messages, the server writes a fhir-replication record to the database within the managed transaction.
However, when there is nothing processing these records (i.e. no separate component deleting rows in this table like in a simple deploy), it will grow unbounded.
We should either remove this project or refactor it so that it can be disabled.
Additionally, some of the metadata fields on these tables are not appropriate for a general-purpose fhir server implementation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions