Want to look into Appwrite, can it fit my needs?

Hey there, I am interested in trying out Appwrite.

I developed an App during unemployment/employer swaps, it's ~75% there, but I just don't have as much time available to fully work on all aspects on it and want to shorten my feature cycles until a public release while also working full-time.

The old app is in raw kubernetes, I am using clerk as an Auth provider and heavily rely on nats for asynchronous service communication and background tasks. I have scraping/synch/worker jobs running every 5-15 minutes, depending on how critical they are.

Here are some of my questions:

• Does Appwrite support proper asynchronous communication between services and fan-out style workflows?
• Does Appwrite support a large amount of functions without spinning up a container for each request?
• Does Appwrite easily support Clerk integration for it's auth while still keeping all features?
• If I have to use Appwrite's auth (eventually keeping more features), can I use Provider Tokens from functions comfortably without worrying about duplicated refreshes invalidating a function? (This has been an issue and a reason to use clerk for me, since they handle token refresh on their end, which made my life a bit easier)

This is just the front of it that might be the most hassle for me, and which may need some digging to get informations for it seems. Would love some answers so I can maybe get a good Idea of how much work moving over to appwrite is.