need to build a micro service architecture using the given requirements

I have attached the requirements in a file and also a picture of full architecture showing the micro service. The Scope of this is to build a Docker based Spring Boot Framework or equivalent that implements the following Features. A. Ability to Listen in on Kafka Topic or Topics for Message existence via Configuration Properties. . B. Ability to Identify Valid(allowed) Message types, which are a configurable via external Configuration Properties. list for the listed Kafka Topic. C. Ability to Identify and collect all 'corrupt/illegal messages' on the Kafka Topic into a common NEW COLLECTION for RCA Analysis. log them as warnings/Errors to the Splunk Platform via AOP implementation. (avoid phi logging) Notification/Alerts and Reconciliation followup needs. (eg : guid, Data Time Stamp, Table name .) D. Ability to select the destination Data Store(MongoDB)details, The target collection store for every allowed message type via Configuration Properties . E. Ability to search for a existing document based on the collection Key or Keys. if found, compare the data and if its different ( ignoring some time and guid details ) then overlay the new record data on the existing one, else ignore. F. Ability to insert a new record if no existing record found in the search assuming its a new entry. G. Ability to Log every successful entry into Splunk with some metadata (no-phi) to identify a specific transaction explicitly/uniquely. H. Ability to log every UN-Successful entry into Splunk with some metadata (no-phi) to identify a specific transaction explicitly/uniquely. I. Ability to Generate Processing Metrics and Estimated times to process the selected records and log it into Splunk. J. Ability to continuously listen in for any message posted on the configured Kafka to be able to process with JIT Mechanism. K. Ability to detect System situations for Source ( Kafka), target ( MongoDB) and Processing Component ( Docker based Spring Boot Micro-Service) and generate Notification/Alerts for Operations team interventions & Decide to Pause the processing (Timer ?). L. Ability to Pause the Processing Component, so that Scheduled maintenance or unscheduled outages can be addressed in a graceful manner and to be able to Schedule or pause Processing windows if need be. M. Ability to process any message type and load into any collection type ,in any order of arrival of messages on the Kafka Topic. N. Ability to Select the Mapping or Business requirements based on each message type and apply to the incoming message before being written to the Data Store or to be applied to the output record of the Search Function to help make the decision on to overwrite or ignore the new message. O. Ability to validate the JSON Message Structure and Critical Content (including Keys ) to make sure that the data is in usable state P. Ability to Store Transaction Information in a Separate NEW COLLECTION ( keys of each collection or critical collection ) which will be used for determining significant events for the processing & generating Cognitive Scale PO Objects Q. Ability to detect Priority if set other than default for the incoming message and process the Level P1 messages ( highest priority) before any lower priority messages are processed.