architect VS deno-mixed-runtimes

I had been running dockeri.co with https://arc.codes/ for pennies a month.

Then, one month, I got a ~$500 bill out of no where.

Docker had changed an api causing my service to return 5xx errors all month. Each error was individually logged to CloudWatch - which racked up a ~$500 bill.

I moved to Cloudflare Workers that day and haven’t moved back.

We use https://github.com/architect/architect to test, provision and deploy the functional web app via GitHub Actions (…whenever they work ;). For the UI/UX we work with https://tailwindui.com and paid them for their great work.

I use https://arc.codes/ for deploying to AWS Lambda/API Gateway. It does a really good job with Remix and NestJS and is easy enough. I like that all I have to do is give a very simple config, and it builds the apps, zips the function code, uploads all my static assets, and then generates and deploys the CloudFormation. I am curious to migrate off as I do have to do some workarounds and it doesn't seem to have a ton of traction.

Not sure why this is downvoted, Fastify is quite popular and the 'generator for everything' approach of Koa didn't really take off.

Architect serverless (https://arc.codes) is pretty good for serverless.

Architect is a heavily opinionated framework for building FWA's, Functional Web Apps. It uses AWS SAM under the hood but provides a layer on top with simplified abstractions that lets developers define and use AWS infrastructure without necessarily knowing what service is backing their "events" construct.

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.

This all is may not be the optimal option for some organisations. The BBC has gone down this route and for more inspiration, McDonald pointed to resources Begin to explore the option of FWA suitability.

[00:00:00] I'm Simon MacDonald the head of developer experience at Begin. And this is my super out of date website.

However, that is not the end of the story. Since then, many services have improved on AWS Lambda's model in ways like ease of use and performance. The first notable FaaS provider was Vercel (ZEIT Now at the time), which was released in April of 2016 and was a lot simpler to use than Lambda. Another selling point was that it integrated well with Next.js, a React framework made by Vercel. Other, newer services also try to be a lot easier, like Begin, although Vercel is still the most popular in that group.

TLDR: tutorial for setting up webhook based serverless AWS apps with Begin. all without managing AWS projects, IAM roles, or connecting EventBridge to a series of Lambdas.

Instead, we'll make it even easier and deploy it to Begin.com. First, push the Arc project to a new GitHub repository. Then head to Begin.com (and make an account if needed) to create a new app.

Begin.com has a generous free tier, so users do not have to worry about costs. But for those on the paid tier, we will soon make this feature available to all users of Begin. We hope that AWS will build this into the platform in a more usable way. Until then, we hope to relieve some of the fear of unexpected bills. If you want to build scalable web apps with Begin sign up for a free account today.

In this post, we will progressively enhance our personal website template to add dark mode functionality. If you don't already have a website deployed via Begin follow our personal website tutorial to deploy the template in 5 minutes, then come back here and get ready to enhance.

To create a Begin account, simply click the Login button on the Begin home page, authorize it with GitHub, and pick a username. That's it!

The final step is to deploy this application on Begin. Begin is the easiest way to deploy your Architect projects to live AWS infrastructure. To do this, create a free Begin account by going to https://begin.com and using your GitHub account to log in. Create a new app and associate it with this repo. Begin will then create hooks to your repo and deploy the app to a staging environment on every git push.