Introduction

Transports allow different protocols and communication channels to be used with the Omniverse microservices stack.

This allows support for, for example, HTTP servers but also queueing infrastructure to be used. All of this without having to change the services themselves. The service does not know, and should not have to worry, about the protocol used to talk to it. This allows to change the entire architecture of how services are used by simply changing some settings. It is possible to have multiple transports enabled for a service, or set of services.

All transports inherit from omni.services.transport.server.base.BaseTransport and this will allow additional and new transports to be added. Transports underneath the hood are also Kit Extensions and as such can be shared amongst teams and published for other users to use.

• HTTP(S)
• Kafka