For now, we mostly focus on building solid foundations and having a design that can be easily extended by the users. It is already run in production at some local companies and we will see whether this is more adoptions in the next months.
Regarding backwards compatibility, we believe that GraphQL's approach is kind of incomplete and that more guarantees can be provided by the server. Nothing concrete yet, but happy to exchange a few ideas!
Prisma is one of the runtime currently supported [1]. Metatype enables you to compose multiple runtimes together. Let's say you have model/struct product (id, name, similarProducts), the two first attributes may be stored in Prisma (like you would do it normally), the third one can come from another runtime such as an HTTP api and the engine will take care of resolving the data together. You can also add an authorization policy on any of the fields.
WMWare labs [1] managed to compile Python/Ruby/PHP into WASM distributions. This works if you want to run the language interpreter but is limited when you want your WASM runtime to run in parallel of your own program. This leads to the creation of the "reactor" concept by the community [2].
In the python WASI reactor, we load the libpython compiled for WASM and add a Rust reactor layer. Currently, it supports dynamic registration of Python lambdas and we are working on adding support for whole functions/packages.
Regarding backwards compatibility, we believe that GraphQL's approach is kind of incomplete and that more guarantees can be provided by the server. Nothing concrete yet, but happy to exchange a few ideas!