https://github.com/klippx/phobosjs-mock

https://github.com/klippx/phobosjs-mock

consumer kafka phobos

Last synced: about 1 year ago
JSON representation

• Host: GitHub
• URL: https://github.com/klippx/phobosjs-mock
• Owner: klippx
• Created: 2017-11-08T11:56:11.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2017-11-09T08:52:49.000Z (over 8 years ago)
• Last Synced: 2025-02-09T09:41:43.300Z (over 1 year ago)
• Topics: consumer, kafka, phobos
• Language: JavaScript
• Size: 11.7 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# phobosjs-mock

Some simple ideas in code how we could be using phobos in practice.

The core ideas are

- No multiprocessing, keep it simple.

  - No need to farm out resources on each node, assume micro instances

  - This alone should greatly reduce complexity of the Phobos code and make it easier to understand/contribute

  - Instead, scale horizontally

  - One service instance <=> one consumer <=> one configuration

- Avoid meta programming and implicit contracts between users' services and phobos

  - The user is in control

  - The code written in services should be simple and readable, even if you don't know kafka (or even phobos!) you should still be able to understand

- Move as much config as possible to `.phobosjs`

- Require as little config as possible inside the users' services, if any.

- Consider possibility of support such as

  - Providing test tools for writing the consumer applications

  - [Possibility to decode avro encoded kafka messages](standaloneConsumer-serializer.js)

  - [Possibility of wrapping the message consumption and dealing with results (errors/success)](standaloneConsumer-messageWrapper.js)

  - phobos-checkpoint-ui

  - phobos-sensor

    - => phobos-prometheus (provide collectors and exporters for internal consumer/producer metrics)

    - => phobos-grafana (provide some rudimentary graphing of the data exported above)