@JetForMe @joannis I mean, that's a question only you can answer right? Are you looking to try a different system?

If you were to do this, I'd love to hear about your experiences though!

@JetForMe @mattiem The Vapor ecosystem’s current design demands ‘bridging’ packages for every library you need to integrate.

One such example is that Vapor has its own lifecycle system. Besides the practical implications, this does not scale at all when a new major release (like Vapor 5) is out.

Besides those pitfalls, Vapor does not embrace structured concurrency whereas Hummingbird 2 does.

Upgrading to Hummingbird 2 might involve some cleaning up, but your codebase will be better for it.