raccoon
raccoon copied to clipboard
Raccoon is a high-throughput, low-latency service to collect events in real-time from your web, mobile apps, and services using multiple network protocols.
PR contains the following changes - - Add support for event acknowledgments based on config parameter `EVENT_ACK` - Doc updates
**Problem Summary** Currently, Raccoon sends acknowledgments to the clients after pushing events to `BufferChannel` and not when published to Kafka. As a result, clients can't retry or resend events in...
**Problem** We (GoJek) use Raccoon currently to source clickstream events from the gojek app. The concrete product proto contains an `event_timestamp` field which the downstream systems such as DWH can...
- Created the basic repo structure - Implemented the Serializer for user events (Json/Proto) - Implemented the Wire Marshaler for raccoon service request/response (json/proto) - Json is the default wire...
**Summary** This reflects on how the raccoon-go-client can be used to communicate with the raccoon service using the different communication protocols. **Proposed solution** The idea is to keep the initialisations...
- Use HTTP to send requests - Supports both JSON and Protobuf TODO: - Requires Pypi Creds to setup push to Pypi - Remove git based package
### Bug - json message isn't serialised with correct Protobuf based JSON encoding standard. - Resulting in failure when sending JSON requests from valid protobuf encoded json string. ### Context:...
**Summary** Currently, Raccoon uses Channels for the intermediate processing of EventRequests, which are then forwarded to the message broker. But it does not solve the problem of loss of events...
This PR fixes panic when multiple requests are made for a topic which does not exist ``` ERRO[2024-04-09T16:39:44+05:30] [worker] Fail to publish message to kafka Broker: Unknown topic or partition...
This PR adds support for AWS Kinesis sink(#78). # Configuration This change introduces the following new configurations * a new `PUBLISHER_TYPE` value called `kinesis` * `PUBLISHER_KINESIS_AWS_REGION` region with the target...