Unless the position *strictly* requires the overlap (e.g. Manufacturing or Program Management), you can apply. The required overlap is the expected team commitment you should abide to, the logistics are up to you to make it work.
If that sounds encouraging, please apply!
I'm surprised on the amount of hate this post has received.
Also, no one talked about what Haoyi has accomplished here (and in the general Scala Community).
There are too many "icons" in the tech industry that are just techlebrities.
Li, OTOH, is one of the most brilliant engineers I've ever seen. It's one of the fewest people I truly admire and I'm sure that most of the fires he describe in his post were already put off, thanks to his initiatives.
Just wanted to bring something nice to the conversation :)
I was a bit surprised to see the announcement about making Redpanda open source (although very interesting for poking around!).
Question: are you, as a company (Vectorized) pursuing the same business model as the Confluent one?
OSS Kafka, but paid official support, cloud, connectors and registry?
We had success with very large customers (enterprise) and also some success with finance company (looking for 0 data loss). The idea is that we can give the kafka API compat system with 10x lower tail latencies for free and still monetize the high end of the market.
I think there is a big shift when you have a single binary. i.e.: no one really complains from running ngix, etc because it's easy to get up and running.
so the gist we wanted to let everyone use it and reserve the right to be the only hosted redpanda provider.
Is there a blog post or docs showing using WASM? I searched your site but couldn't find details.
I've failed to grasp if it's an "alternative plugin-engine" kind of system to extend Redpanda, or you're storing data as WASM and therefore it's executable (to take your example: GDPR compliant auto-expire if it's past a certain date).
feel free to embed, ingest customer data, run on a saas application. The only restriction is hosting redpanda as as service for other customers (Think AWS MKS)
If you have any questions or think your use may be confusing please reach out to us.
If I am reading the fields of this implementation of BSL correctly, it will be open-source software in 10 years, when it converts to Apache 2.0, but not today. Until then, the license does not comply with the open source definition due to field of use restrictions.
" Our intention is to deter cloud providers from offering our work as a service. For 99.999% of you, restrictions will not apply - welcome to our community!"
This is simply not true. The restriction applies to 100% of everyone using the software under the license.
If an alternative service provider can't legally host the service for me, I am restricted from selecting an alternative vendor if my needs converge from the available vendors offerings.
Yes, all of us are bound by the terms alike but I think everyone understands it was meant as commercial and non-commercial use for 99.999% of you will not trigger the respective clauses in the license. And the post title literally says "Redpanda is now Free & Source Available".
