Optimizing Performance with WeWeb and Xehanl: Fetch Collection vs Request Data
In this meeting, the State Changers were discussing the performance optimization of data fetching process in WeWeb. One of the participants was concerned with whether there was a better practice between using 'fetch a collection' or 'request data from Xehanl' when triggering workflows. The consensus was that using 'fetch collection' could be more efficient since if the collection was up to date, the system would not need to update. However, if the freshest data is needed and WeWeb isn't providing it, that would require more of a direct request.
While discussing this, the point was raised that it’s okay to use these tools in unconventional ways to achieve the desired results. The advantage of no code tools like WeWeb is their flexibility and forgiveness. During a prototyping phase, it was emphasized that progress should not be slowed down by the attempt to use tools in a 'strictly correct' way. It was mentioned that learning and discovering more about the tool should be priority.
Participants were encouraged to allow for learning, flexibility and iteration while using these tools. The meeting ended with the intent of continuing the discussion in subsequent sessions. Relevant tools mentioned include WeWeb and Xano.