jeffail

5 ms·

1.
by jeffail 1y ago
Personally, I'm happy to see them evolving it with my juices left intact. When we transitioned benthos.dev to https://docs.redpanda.com/redpanda-connect we gained a much larger (and more competent) docs team, but as a
2.
by jeffail 2y ago
Sure, if they change the MIT license of the core engine then you could fork it at that point. What they're doing right now is taking on a much larger maintainence burden than potentially necessary and fragmenting the ecosystem at the s
3.
by jeffail 2y ago
It absolutely doesn't need a fork. The entire project is designed specifically to allow vendors and users to have their own ecosystem of plugins and they can all compile and integrate seamlessly. I'll be explaining live in 30 mins
4.
by jeffail 2y ago
Hey it's Ash (the maintainer being talked about in the blog). I'm not one for fork drama and I haven't had a chance to fully read the blog so I don't have a lot to say. However, this is a full fork of the entire codebase
5.
by jeffail 4y ago
Sorry to hear that, unfortunately you can't please everyone whilst also having fun, and my open source work is unapologetically fueled by fun.
6.
by jeffail 4y ago
Thanks for sharing, this is awesome to hear!
7.
by jeffail 4y ago
Yeah that's my bad, the site assumes you already know what benthos is as it's an early stages UI for it. The best place to start is https://www.benthos.dev , or if you like dumb videos: https://youtu.be/
8.
by jeffail 4y ago
Hey! The visuals are all via https://reactflow.dev/ , which has been pretty awesome to use.
9.
by jeffail 4y ago
If I want to achieve something then I find the joy in pursuing it, at which point I will naturally do it when I'm capable and will do other things when I'm not. Letting my attention float around freely (within limits obviously) of
10.
by jeffail 4y ago
Hey everyone, this is a video I put together summarising a decades worth of stream processing delivery guarantee misconceptions and bugs that I've seen frequently. I'm not trying to scare anyone away from stream processing, in fac
11.
The Dodgy State of Stream Processing Delivery Guarantees(youtube.com)
3 points by jeffail 4y ago|1 comments
12.
Ask HN: Bing blocking FOSS docs website, how do I find out why?
2 points by jeffail 4y ago|0 comments
13.
by jeffail 4y ago
I hope one day https://www.benthos.dev will feature on one of these logo collages and I can finally retire to hobby watchmaking or something.
14.
Change Data Capture is having a moment. Why?(materialize.com)
3 points by jeffail 5y ago|0 comments
15.
by jeffail 5y ago
Anecdotally I'd say professions that often double up as a hobby and don't have a significant material or energy cost to exercise will be more susceptible to burn out. If you're _really_ into software engineering and struggle
16.
Building a Mapping Language in Go with Parser Combinators(youtube.com)
1 points by jeffail 6y ago|0 comments
17.
by jeffail 6y ago
Maintaining an OS project definitely gives you a crash course in (and boosted respect for) non-engineering roles at tech companies. However, I'd say if you're maintaining something and don't enjoy one or more of these hats th
18.
by jeffail 6y ago
I'm massively rooting for this. I really wanted to use Gitter as the official chat for my projects, but the experience was just so painful that I ended up fragmenting the community across Discord and a gated Slack. I would love to have
19.
A dull stream processor in Go(benthos.dev)
3 points by jeffail 6y ago|0 comments
20.
Enriching 450M Docs Daily with a Boring Stream Processor(underthehood.meltwater.com)
4 points by jeffail 7y ago|0 comments
21.
by jeffail 7y ago
That makes more sense, thanks for clarifying. Still, assuming there are no other edge cases there, it doesn't address the other problem where a hypothetical consumer of the output topic is reading an at-least-once feed of your exactly-
22.
by jeffail 7y ago
Yeah but the first time it was read the key was stored in RocksDB, so the second time it gets consumed after the crash: "If the message already exists in RocksDB, the worker simply will not publish it to the output topic and update the
23.
by jeffail 7y ago
"What’s more, we want to ensure the information about which events we’ve seen is written durably so we can recover from a crash, and that we never produce duplicate messages in our output." Your processor is described as writing f
24.
by jeffail 7y ago
"amounts to 1.5% of its worldwide turnover in 2017" I imagine that's a significant sum but I'm struggling to get my head around it. If so then good for the ICO I suppose. I remember reading endless comments a few years b
25.
by jeffail 8y ago
Processor implementations are able to carry their own state, or share state across worker threads or deployments using their own mechanisms, but Benthos doesn't provide any tooling for that. None of the processors you get out of the bo
26.
by jeffail 8y ago
All Benthos processors are stateless, except for a few such as batch, combine, etc, which do basic tasks such as building up batches from consecutive messages. It's possible to create sliding window processors on top of Benthos, but th
27.
by jeffail 8y ago
Yeah just boring. Benthos is mostly a collection of standard processors for doing boring stuff.
28.
by jeffail 8y ago
Hey, the HTTP output has a fixed number of retries, after which you could either have some mechanism in place to fall back on or by default it will simply continue the retries again whilst blocking upstream. You might also be interested in
29.
by jeffail 8y ago
Hey, Benthos doesn't yet provide any general tooling for exactly-once processing like Wallaroo does, that's possibly a goal for the future. My main focus has been providing general purpose stateless processors. So you can build a
30.
by jeffail 8y ago
Hey everyone, author here. We use Benthos as a general stream swiss army knife for all the dull tasks, but you can also use it as a framework for writing your own stream processors in Go. It doesn't provide any tools for idempotent cal

More ›