Create pool of active producers. Start pool on module launch, close on shutdown. Reuse connections.

Add max/min pool sizes.

Do not subscribe to messages you're not going to process

OR

Lower log lever for this type of messages

Race condition on start (Kafka consumers start working before DB is configured)

OR

Periodical DB shutdown after SRS restart. Jobs get stuck if not able to update status in DB (messages ACKed even if we could not process them)

Need investigation / check

Investigate the issue with DB (possible OOM on PG server)

Performance

Stability/Reliability

Significantly decrease size of payload:

1. Remove immutable parts. Instead fetch them on demand and cache locally for reuse.
2. Change message handling mechanism (currently relies on pt1 - profile) (optional)
3. Move archiving to Kafka instead of module level

Need investigation (possible solution - configure rate limiter)

Relates to number 4

4

Generate "INSTANCE CREATED" from mod-inventory. Consume in SRS to update HRID in BIB and in INVENTORY to continue processing.

Remove unnecessary topics (* ready for post processing and hrid set)

If we have infrastructure issue (like DB not available, module being restarted or network failure), we are sending DI_ERROR instead of retrying

Do not ACK messages in Kafka if there's not a logic, but infrastructure error/exception. Split failed processing results into 2 categories:

1. IO errors - do not ack. retry until fixed
2. Business logic - DI_ERROR and Ack current message