Page History

...

Kafka Messaging (pub/sub)
* Each OMAS will listen to ONE incoming omas kafka topic (per omas) for requests to process
* Each OMAS will listen to OMRS kafka topic so as to respond to changes in the metadata repostitory
* Deployment-time properties will configure the topic names to be used
* Out of order messages need to be handled "sensibly" [requires further discussion] & clustered environments catered for
* Messaging infrastructure should be pluggable, but only kafka will be implemented

Language/Bindings
 * REST/Kafka - language neutral
 * Java client (remote) - improves ease of use 
 * Python - not initially but expressed as a language of choice for data scientists

Documentation
* A skeleton Java implementation will initially be committed to generate Swagger API
* When the community is broadly happy the implementation will be filled out