#Qwik in serverless

4 messages · Page 1 of 1 (latest)

tawdry arrow
#

We are starting our first Qwik project. We are rebuilding a 10 year old project using the serverless.com backend framework in AWS services and GoLang. our tool has gotten slow so we are rebuilding with speed as the primary focus. I have watched dozens of hours of video on qwik, and now we are ready to take the next step to see if we can build something to replace our front end. we are committed to a qwik like architecture, and we want to see if we can use qwik.

My question is what should we know before we get started, what are the obvious pitfalls we are likely to encounter using this backend approach? I hope I can start a dialog here to help me clarify my thinking and get a good start to this project. Thanks for your help!

fiery prism
#

Some thoughts:

  1. Qwik is in beta, and Qwik City (the meta-framework) is in a pre-beta. There are still a lot of bugs.
  2. Qwik expects to run on a Javascript backend for server-side rendering, unless the pages are static and pre-rendered. This might prevent you from using only Go. Current supported runtimes: https://qwik.builder.io/integrations/integration/overview/
  3. Qwik is fast, yes, but depending on where your existing performance bottleneck is, it's possible that Qwik won't bring much benefit.
tawdry arrow
#

Thanks for the feedback

tawdry arrow
#

I am trying to understand how Qwik works
is qwik only a client side code?
that pulls resources from server?
or does it require that we install the qwik framework on the server too (not ideal for serverless backend build with GO microservices)
If Qwik can be only client side, that is good
then GO can provide all the data and assets server side