agallego
Joined 15 years ago
Karma
310
Submissions
170
Member since
Dec 29
Recent submissions
Comment · 1 month ago
You can use redpanda with interrupts just fine (no fan noise). You don’t need to busy poll for low resource envs. Same for sys alloc
Comment · 11 months ago
Hmm. Strange. DM me details. Haven’t heard of anything like that.
Comment · 1 year ago
What we found with RPCN (redpanda connect)/old benthos is that most systems are very slow and only cpu intensive things require manual CPU instruction optimizations like the snowflake connector we wrote (https://docs.redpanda.com/redpanda-connect/components/output...). The bulk of it is just about completeness. Go feels like the Perl of the 2020s. Cool little libs for just about everything.
Comment · 1 year ago
It is not FUD. It is deterministic. Reproducible on your laptop. Out of all the banks I work with only a handful of use cases use rf=5. Defaults matter, because most people do not change them.
Comment · 1 year ago
coo cool right on.
Comment · 1 year ago
Redpanda cloud doesn’t limit tput. Most ppl get a bigger discount at high volumes. We have customers in 10s of GB/s. Confluent has those volumes too.
Comment · 2 years ago
incorrect. the intend is to have it be a project that is thriving, see the last 2 additional partnerships that landed as apach2 connectors: https://redpanda.com/blog/redpanda-connect w/ peerdb, and ockam.
Comment · 2 years ago
we trippled the team. added 3 meaningful connectors for CDC and zero-trust as well multi-lang SDK and kept 99% of the connectors available for ppl to make money on... as well as the core engine remaining MIT. This is about them not wanting to depend on redpanda products which is ok, but the whole thing is hard to believe from a company that has no open source products. it's more like "hey, i don't like it."
Comment · 2 years ago
you may have not read the blog post i wrote. the engine remains MIT because we had customers that had embedded this in their app and it made sense to keep that. it is 100% about not having to call it "redpanda x" https://redpanda.com/blog/redpanda-connect
at the end of the day, there is plenty of ppl that are making money on this that is not us and that's cool too. we just need to retain the brand of the code we maintain. that's really the thing that matters.
Comment · 2 years ago
let's call it what it is. warp never reached out. they do not want to have the name "redpanda" in their UI. that's all. They can* make money on 223 out of 225 connectors. More over the engine* remains MIT.
Comment · 2 years ago
Hey jannesan this is untrue. We pay for ZoomInfo which gives us emails on search engines results. No one is manually filtering on your GitHub. But it should have a link to unsubscribe. Let me know if it doesn’t work and happy to remove. We use a mailing list provider which manages the unsub for us.
Comment · 2 years ago
Oh that’s cool. How do plugins/add ons work with clickhouse
Comment · 2 years ago
500MB for such a complete product is tiny! The largest CDN in the world ships 10GB+ binaries. 1G is common for large code bases if you link things statically. The bloat tends to come from transitive dependencies, most direct code is small in size
Comment · 2 years ago
Curious as to how the code base evolved after forking from clickhouse
Comment · 3 years ago
that's a littlebit of a stretch. when you say "no shortage" - outside of redpanda what product exists that actually compete in all deployment modes?
it's a misconception that redpanda is simply a better kafka. the way to think about it is that is a new storage engine, from scratch, that speaks the kafka protocol. similar to all of the pgsql companies in a different space, i.e.: big table pgsql support is not a better postgres, fundamentally different tech. you can read the src and design here: https://github.com/redpanda-data/redpanda. or an electric car is not the same as a combustion engine, but only similar in that they are cars that take you from point a to point b.
Personal site: alexgallego.org Twitter: twitter.com/emaxerrno