Is the project still actively maintained?

[amrynsky]

We’ve been looking into parallel-consumer and really like it so far - it seems like a great fit for our use case. Before we take a production dependency on it though, we’re trying to understand the current maintenance and roadmap story:

• Is the project still actively maintained? In particular, are security vulnerabilities fixed in a timely way? It looks like there weren’t many releases last year.

• Is there an actual roadmap, or is it more “on‑demand” fixes and changes as issues come up?

Some features we’d really like (e.g., partition‑level backpressure - #540) don’t make it clear whether they’re on the roadmap or not.

Some open issues look potentially dangerous for production use (paused consumption across multiple consumers - #857), so it would be super helpful to understand how you’re thinking about them and whether fixes are planned.

It would also be great to hear from others who are running this in production today and what their experience has been. Any insight you can share here would really help us decide whether we can safely adopt the library.

Thanks for all the work that’s gone into it so far!

[sharifahmad2061]

I found missing trace_id in logs from parallel consumer thread pool and vert.x event loop. our own logs in user function for vert.x are missing it as well.