hashmapinc / hashmapinc/Tempus
Separating MQTT broker out of Tempus
Open
backlog
Spike
Tempus/Application
- Dominant language
- Java
- Stars
- 32
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Currently, when WITSML data ingestion through gateway runs for high frequency objects. Tempus UI slows down due to the load. To mitigiate this problem instead of scaling entire Tempus application. We need to separate MQTT broker out of Tempus.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.