Could we a slimmer version of pitchfork!
jcchavezs opened this issue · 2 comments
jcchavezs commented
Describe the feature
Make pitchfork slimmer
Rational
Pitchfork has great potential for different things, one of them being a sidecar for ingesting zipkin data. Ideally we should remove all the overhead possible so it consumes the less data possible. I think we could learn from the changes in https://github.com/openzipkin/zipkin/pull/2818/files to get an idea on how we could make pitchfork slimmer.
Ping @worldtiki @eleduardo
worldtiki commented
Hi @jcchavezs :)
Imo there's 2 paths we could take:
- A small lighter version of Pitchfork written in Go with the goal of being used as a sidecar. I'm pretty sure we can build something that would not be as performant but would be much more resource efficient.
- A similar approach to the one you mentioned. I'm not sure how much effort we should put into this though since the savings would not be as significant. We could probably wait a bit more and explore an integration with Graalvm when it becomes more widely available for spring boot?
codefromthecrypt commented
ps I have seen some buzz around boot 2.4 being the one that makes things
like this easier. here is a sample project..
https://github.com/spring-projects-experimental/spring-graalvm-native/tree/master/spring-graalvm-native-samples/webflux-netty
…On Sat, Aug 15, 2020, 6:31 PM worldtiki ***@***.***> wrote:
Hi @jcchavezs <https://github.com/jcchavezs> :)
Imo there's 2 paths we could take:
- A small lighter version of Pitchfork written in Go with the goal of
being used as a sidecar. I'm pretty sure we can build something that would
not be as performant but would be much more resource efficient.
- A similar approach to the one you mentioned. I'm not sure how much
effort we should put into this though since the savings would not be as
significant. We could probably wait a bit more and explore an integration
with Graalvm when it becomes more widely available for spring boot?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPVV4YWIQZX6R4WDKGQSTSAZPXDANCNFSM4PLTUFXQ>
.