tevr-asr-tool VS redpanda

Do some cool open source stuff. Since August 9th, I received about 50 job offers mentioning this repo: https://github.com/DeutscheKI/tevr-asr-tool Most of them were senior engineer or AI researcher, with a few CTO / co-founder offers sprinkled in. I'm not in the market and this was a bit unexpected to me, but those emails sounded like they would pay well. And most was remote for US companies.

Me, because I plan to extend to realtime processing: https://github.com/DeutscheKI/tevr-asr-tool

Also, all the performance critical stuff on my production servers is C++ with JNI or pybind wrappers.

The unique work that makes this speech recognition superior to other tools is in those 284 lines of code: https://github.com/DeutscheKI/tevr-asr-tool/blob/master/tevr...

That's a custom-designed beam search decoder implemented in C++ and based on the research for my TEVR paper. It increases performance by a relative 16% reduction in word error rate.

Stream-processing platforms such as Apache Kafka, Apache Pulsar, or Redpanda are specifically engineered to foster event-driven communication in a distributed system and they can be a great choice for developing loosely coupled applications. Stream processing platforms analyze data in motion, offering near-zero latency advantages. For example, consider an alert system for monitoring factory equipment. If a machine's temperature exceeds a certain threshold, a streaming platform can instantly trigger an alert and engineers do timely maintenance.

Yeah it’s just the stack switching itself that is a handful of cycles, but there is not much more overhead for the full VM switch if you structure your embedding the right way. Code the code is source available if you want to peek at it!

https://github.com/redpanda-data/redpanda/blob/dev/src/v/was...

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.

Redpanda with the MongoDB Debezium Connector installed. We use Redpanda as a Kafka broker.

And Kafka + Kafka Connect has https://www.confluent.io/ https://aiven.io/ https://upstash.com/ (and not quite Kafka, but protocol-compatible, https://redpanda.com/)

There exists a C++ project which was created after Rust the language was available. github.com/redpanda-data/redpanda/

I suggest you check out io_uring and thread per core architecture. Applications like scylladb and redpanda have thread per core architecture and use io_uring for async io.

Redpanda