Re:Launch HN: SigNoz (YC W21) – Open-source alternative to D...
by jwatte on Tuesday February 09, 2021 @03:19PM
(#26081970)
Even if you maintain Kafka for business logic, you don't want to run your observability in the same Kafka cluster, because then when the business Kafka goes down, how will you debug it?
Re:Launch HN: SigNoz (YC W21) – Open-source alternative to D...
by ankitnayan on Tuesday February 09, 2021 @03:39PM
(#26082137)
Correct, Ideally monitoring stack should be outside the blast radius of other applications. Will handling another Kafka cluster (probably smaller than business Kafka) be a pain for the team given the team already knows managing one business Kafka. What do you think?
Re:Launch HN: SigNoz (YC W21) – Open-source alternative to D...
by ankitnayan on Tuesday February 09, 2021 @02:28PM
(#26081517)
I completely agree with you. For companies not already using Kafka, this will ask for a big commitment to self-host Kafka.
You mentioned a great approach. Queueing system as a plugin. Thanks
If a company is not already using Kafka, they wouldn’t want to maintain it “just” to have a self hosted APM system.
If I could make a recommendation to the developers of this system, it would be to focus on the interface with the streaming platform, before the implementation of using Kafka to support that interface.
Ideally, one should be able to plug in and out the queueing system of preference.
This will help adoption, and avoid coupling the success of your project to the implementation and success of Kafka.