Wappler has been offering the latest technologies to all users in the easiest and fastest way for a very long time, and it does this successfully. I also started to use these technologies in projects. Our successful results showed us that we can also use wappler in industrial solutions. ( such as scada , mes and IoT solutions ) . Wappler is now a potential application that can be used not only for a standard web app, but also for real-life industrial solutions. For example, wappler now supports natively with side solutions such as redis, treafik. However, it has not yet taken a “full” step for IoT solutions that will be used very frequently in the future. What I want to say right here is in Wappler;
- time-series database support,
- MQTT support
- GraphQL,
etc…
There is no such basic support yet. You can think of the graphql support I mentioned in my previous posts as follows.
Now imagine that you are creating a page in Wappler in SPA model and you add server connect for the queries you need for each page. You can see all the JSON that is needed or not in that page in the JSON response from the user API that logs into the page. Of course, you can store the fields you do not want in wappler in json, but if you want to use the similar query in a different field, you create a new server action and the process proceeds in this way. Here graphql doesn’t process fields you don’t need and avoids load generation. In addition, graphql’s other purpose is to pull data from more than one data source at the same time. Of course, there is a similar structure wappler now. You can pull data from different sources in Group and parallel. But this solution is not very flexible. It will take an incredibly long time to make a full comparison of this and fit it in one post, but when you research graphql deeply and examine it by thinking about wappler, what I mean will be fully understood.
Other time-series and MQTT support is one of the must-haves for communication with Iot devices. Currently, a small-scale realtime stock, chat, etc. applications can be made with Wappler, it provides a lot of resources and mysql etc. as a database. You can use it, it won’t be too much trouble. But these databases are relational databases and are not designed for this purpose .
It is also a part of this structure to put the data flowing with mqtt in a queue and to avoid problems with delays . I think it is necessary for Wappler to see these shortcomings and move on to industrial use before it’s too late.
Apart from that, socket connection is popularly used in chat software. Apart from that, its main purpose is to process instant information and present instant information to users. . ( there are many more usage topics ) . I used socket connection with voip in my last project. (in the call center - agent console). Now I will use scada and wappler to the end, let’s see what happens 
