This change vastly simplifies the code of individual delivery services, while adding extra protection against service failure.
The BaseWriter class accepts messages from logical_timeseries RabbitMQ exchange and writes them to a service-specific database table. A thread reads from the table and invokes the service-specific on_message method to deliver the message to the destination platform. on_message may return ok, fail, or retry. The service-specific code is responsible to deciding how many times a message should be retried before being marked as a fail.
The Ubidots client code was updated to include the broker correlation id in its log messages, and also have the 0.3s delay before calls to adding data which is probably what caused some of the error responses we're seeing.
This change vastly simplifies the code of individual delivery services, while adding extra protection against service failure.
The
BaseWriterclass accepts messages fromlogical_timeseriesRabbitMQ exchange and writes them to a service-specific database table. A thread reads from the table and invokes the service-specificon_messagemethod to deliver the message to the destination platform.on_messagemay return ok, fail, or retry. The service-specific code is responsible to deciding how many times a message should be retried before being marked as a fail.The Ubidots client code was updated to include the broker correlation id in its log messages, and also have the 0.3s delay before calls to adding data which is probably what caused some of the error responses we're seeing.