gomodest-template VS serverless-graphql

Its too early for a roadmap. I have tried different approaches and rejected them: https://github.com/adnaan/gomodest-template, https://github.com/goliveview/examples. I want the library to be have a great UX, good for moderately complex apps while building tech which is maintainable(no new rendering layer engine). I could use some help brainstorming the approaches though.

Oh wow someone finally went ahead with the server rendered js in Go ! Looks great. I have been experimenting various ways to build web apps in Go: https://github.com/adnaan/gomodest-template. I have landed on pursuing one approach more deeply: server rendered html templates over websockets. Don’t have a lot of code right now but here are some examples: https://github.com/goliveview/examples.

Since early this year, I started working on https://gomodest-template.fly.dev/samples, https://github.com/adnaan/gomodest-template to experiment with various ways to build user interfaces in Go, html and a bit of javascript. Now, I have taken all the learnings from gomodest-template and started working on https://github.com/goliveview/ . Its super early work.

So I have been exploring server side rendered Go web apps using only sprinkles & spots of javascript: source: gomodest-template , live demo .

I have built an app template which uses Go html/template package to render html on the server. The app is enhanced using sprinkles of javascript(stimulusjs, svelte single file components) on the client, wherever needed.

1. template: https://github.com/adnaan/gomodest-template

gomodest-template

Since then, the ecosystem has changed. Using the Serverless Framework makes deployment simpler. We released the managed Tracetest App making any serverless-based systems simpler to instrument and test. You can now test public-facing apps with no infra overhead!

We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!

When we think about AWS serverless service, the first thing that comes to our mind is Lambda function. Yes, the quickest way to deploy this backend Express JS app to AWS is to deploy it as a Lambda function. The easiest way is using Serverless Framework.

Serverless Framework: https://www.serverless.com/

Github | Website

In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.

Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.

1 - Serverless + AWS CDK + Lift: An integration that amps up the traditional Serverless Framework with Lift's static frontend construct and CDK's robust infra definition.

It's a bit easier in Python if you use tools like https://www.serverless.com/. I'm not sure if Rust has something similar yet.

Serverless