Event Receiver

Introduction

The Event Receiver is the entry point for events coming into BAM. The event receiver will be responsible for a myriad of tasks. These are listed below:

  1. Initializing the thrift authentication service
  2. Initializing the thrift receiver service
  3. Storing the events in the respective tenent's keyspace
  4. Extension of the receiver
Even reciever is shown in the below figure, there you can notice the key components to store the recieved events. in the Important aspects of the Event Receiver as discussed below.

Event Reciever

The Thrift Authentication Service

The Thrift Authentication Service will be responsible for authenticating and authorizing the source of the events, before the events reach the reseiver service. This service will check the credentials set by the data agent against the BAM user base. It will be hosted on the https port of the BAM server. There is no additional configuration needed to use this service.

The Thrift Receiver Service

The Thrift Receiver service will queue the received messages and release any threads, so the threads can process additional messages. The queued messages will then be stored into respective tenent's data stores.

Extending the Event Receiver to support additional protocols/message formats

NOTE: This is WIP and will not be available in the 2.0.0-alpha version

The Event Receiver currently supports The Thrift socket (binary) protocol and Thrift over HTTP. Room for extension to add additional protocols are under consideration. In the future releases, Web Services, REST, JMS and other protocols will added to support sending events over these protocols/message formats.