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?
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.
i.e.: think GDPR compliance as long as your data streams are in JSON or some predefined format.
WASM basically allows us to push computational guarantees to the storage engine itself without a separate cluster.
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).
It seems totally fair to me. Good luck with this approach. I think yours odds are good.
1. You can't just take this and make money from it
2. They don't accept or expect external inputs.
Its the same as cockroachdb in that regard
If you have any questions or think your use may be confusing please reach out to us.
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.
Further, it still isn't open source.