GitHub user thyseus closed a discussion: "hook" for incoming message
I want to discuss with you if it is a good idea to implement a "hook" feature
on the iggy server side.
What do i mean with "hook" ?
In case a message is incoming, i want to be able to configure one or several
"hooks" that will point to a script file or binary that gets executed by the
iggy server.
Why is this useful ?
a) i could do mundane tasks that dont require a real consumer implementation,
like logs or just pushing the incoming messages somewhere else, really quickly
b) In my use case i have several applications that are written in python, php,
rust and many more. Even some, where there is no SDK for iggy yet (php - i have
done a primitive one for myself).
Instead of implementing a consumer for each of this applications i could
simply register a "hook" in a stream that executes a `php artisan
receive-message '{"payload": "example"}'`. This also has the advantage that my
consumers dont need to "poll" the iggy server but gets the message immediately.
(I know that many advantages of a proper "consumer" implementation are missing
then; but there may be cases where that is ok).
What do you think ?
GitHub link: https://github.com/apache/iggy/discussions/1641
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
