architect VS htmx

I work for vercel but I highly recommend a host like us because we make it a lot easier to manage a lambda environment and being a lot more to the table (cdn, edge functions, etc). If you want to go your own I really like architect https://arc.codes too. It really depends on your traffic and application patterns but cold starts can be virtually nil.

It uses: - Remix for the frontend - Architect for the backend

Alternately, use Architect. Architect is a 3rd party developer experience that builds on top of AWS SAM. Architect includes a TypeScript plugin.

For us at Begin and Architect, tape has been in use for several years. tape has a stable and straightforward API, routine maintenance updates, and outputs TAP, making it really versatile. While TAP is legible, it's not the most human-readable format. Fortunately, several TAP reporters can help display results for developers. Until recently, Begin's TAP reporter of choice was tap-spec. Sadly tap-spec wasn't kept up to date and npm began reporting vulnerabilities.

Architect will help set up various HTTP routes (API Gateway endpoints backed by Lambda functions) to handle incoming webhook data.

Instead, let’s leverage the power and scale of AWS with the ease of Architect and Begin. Without managing AWS projects, IAM roles, or connecting EventBridge to a series of Lambdas.

I would start with separating the frontend and backend, as some others have suggested. I would probably use react but could try svelte or vue also. In the start you can mock the backend or have a memory-kept version of it.

For backend (the api) I would go for c# or nodejs (maybe with nextjs). I might combine this with a serverless solution like Architect.

https://github.com/architect/architect

Use https://htmx.org and wtforms, they work great together.

I'm trying to show where it could go with htmx: https://htmx.org

What we need is for HTML to get going as a hypermedia again, to make the hypermedia architecture viable for a larger set of web applications. It's been stalled at anchors and forms (with only GET and POST!) for decades.

I'm trying to show where it could go with htmx:

https://htmx.org

Hypermedia (in particular the uniform interface) is what made the web special and there's no reason it can't be improved along the lines of htmx/unpoly/etc.

We don't need something new. We need to take the original concepts of the web (REST/HATEOAS/Hypermedia) seriously.

htmx.

Have you looked into htmx?

If you end up resorting to javascript for this I recommend you use htmx

POST requests fail when browsers send preflight requests. Removing the non-standard headers doesn't prevent the request from being sent, like suggested in this issue.