We might want to start a new thread on this topic for Adalo v Xano as backend performance. Using this component will speed up all internal and external collections.
It is a non-trivial topic, so I will try to simplify it as best as possible.
An Adalo app has a very specific and ridged data format and structure so that the No-Code design tool can be used without needing to know the underlying data structure (a lot of work was put in to making displaying data as easy as possible.
What this means is, using an Adalo database works like this
My application will ask Adalo server for the information I want, Adalo will get the data from the Adalo database and return the data to me.
When using Xano as a backend it works like this
My application will ask Adalo server for the information I want, Adalo will as Xano for the information it wants, Xano will get the data from he database and return it to Adalo, Adalo will transform the information into something it understand, then it will return the data to me.
SO, if you have an Adalo table of messages, moving that to Xano will not make too much difference, probably slow it down a little. I do not know the databases used by Adalo or Xano (or others), but judging by the structures I will take a guess the BOTH use MongoDB. So there is probably little performance increase on CRUD (create, retrieve, update, delete) data, but Xano will take extra steps so probably take longer.
If we removed Adalo server from the equation and wrote custom components for everything to go direct to Xano without passing through Adalo, we lose the Magic Text and other features!
My opinion on the matter is:
If you need to do side-effects on data, like create complex conditional records that requires backend programming, Xano will fit the bill. If you can do what you need to do using only Adalo database, stick with Adalo rather than any other backend. Adalo will continue to work on improving their servers and it will get better over time.