WeWeb Performance Issues and Potential Solutions: Migration to Digital Ocean

In this meeting, the State Changers discuss the performance issues of a WeWeb application. They discuss the high latency of the application's page transition times, which they attribute to the geographical distance from the server of WeWeb, the hosting platform. Participant Michael brings up his concern about an API response time reported in the application's console log taking six seconds, which is significantly longer than expected. To address this issue, the plan is to export the code of the WeWeb application and host it on a server closer to Michael's geographical location to improve performance.

Among the discussed solutions is using DigitalOcean, a cloud server providing company, which offers servers in different locations worldwide, including Sydney, where Michael is presumably located. Despite technical issues in creating an account, the State Changers suggest that hosting on a DigitalOcean server in Sydney could resolve their problem. The focus of the meeting then shifts as they start to help another participant, Paul. Throughout the meeting, one keyword from the provided list has been mentioned: WeWeb. The other provided keywords such as "Xano", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", and "AI21" were not directly mentioned during this conversation.

(Source: State Change Office Hours 9/21/2023 )

State Change Members Can View The Video Here

View This Video Now

Join State Change Risk-Free