aioredis VS faust

First, it was aioredis library. We are using sentinel based client because with this we can achieve failover easily. Aioredis spawn pool of connections, that transparently reconnects (and here third thing — FOREVER, hello DDOS) to our sentinel nodes, and then to master node. It supposed to do so. Also, we found that if you are not limiting maximum connections count, library will do it for you and set it as 2 ** 31 (here you can see it) — this is fourth thing. Furthermore, pool in our version (2.0.1) not closing automatically, and it makes the problem worse.

I'm hoping to leverage Redis with my project, and I was curious as to if anyone had any general pointers as to how best to manage the DB connection. I'm using aioredis such that I can leverage the async functionality, but I haven't been very happy with the library's documentation surrounding how best to leverage the connection pool. Most of the examples create and tear down the pool immediately without showing how best to manage its lifespan.

We have many similar ideas and paradigms, as one would expect from modern frameworks tackling the same problem. However, Faust has been deprecated and no longer managed or supported (there is a fork being maintained by the community at https://github.com/faust-streaming/faust). I guess Robinhood at some point decided not to spend any more resources on it, an often destiny of such side projects by large corporations. On the other hand, we hope to stay around for a long time and build to a framework and a community that loves it. This initial version was built using many libraries in order to have a working system and to gather feedback from the large community. We plan to replace eventually all, or at least most of dependancies, and replace then with Rust lib with Python bindings.

Just wanted to add that there is an actively maintained fork called faust-streaming, you can find it here: https://github.com/faust-streaming/faust

That's the basics yes. You have a pletora of things coming next. One is "Windowing" mentioned in the article, it's well explained and maybe it looks simple, but when you start with it, takes some time to wrap your mind around it.

The other things in kafka world are stateful transformations, which you would normally do using Java's Flink. The closest in python is Faust (the fork) [0]. What are stateful aggregations? something like doing SQL on top of a topic: group_by, count, reduce, and joins. So similar to SQL that you have kSQL [1].

Consumer groups IMO falls under basic usage, if you need to scale, take a look at it, and what are partitions and replicas, with that in mind, you'll be ok.

[0]: https://github.com/faust-streaming/faust

[1]: https://www.confluent.io/blog/ksql-streaming-sql-for-apache-...

The forked one, https://github.com/faust-streaming/faust, has been updated but still doesn’t seem to support joins.

Faust: Python framework

I’d like to use Python for this so I came across Faust but I’m not sure if it’s possible to create HTTP requests through Faust or if there are better alternatives.

There is a community fork which was stale for a while but got a new commit a couple days ago, this one might be usable, but is still quite risky (70 open issues etc.): https://github.com/faust-streaming/faust

There is a community which forked and actively develops faust, here’s the https://github.com/faust-streaming/faust

Hi, thanks for the answer, I'm actually using virtualenv with the requirements of the file associated with the example. However I wanted to tell you that due to covid the project is suspended but only temporarily, but there is an active fork https://github.com/faust-streaming/faust. But the example in the fork doesn't work either.