girouette VS serverless-graphql

Some of the bigger changes: - Code is now split up into a set of independent libraries. e.g. you can depend on the biff.crux lib if you want to use Biff's authorization rules or query subscriptions in an existing project. - Deployment is much simpler. Previously I was experimenting with a weird terraform setup where the config was managed by biff, but I decided it was more trouble than it was worth. Now there's just a bash script for provisioning an ubuntu server, including push-to-deploy. (Or you can stick the uberjar + env file wherever else you want). - Replaced Tailwind with Girouette! No more tooling needed outside the main clj process.

I seldom write CSS. I tried tailwindcss on one of my recent projects that required to closely follow a custom design (a portfolio for a graphic designer friend). I like it, with some caveats.

Main benefit for me is that I don't need to remember how to write css. 95% of what I need is a shortcut away from tailwind docs. The result is "prettier" than any other website-from-scratch I've done (that's purely on me, not much css practice). Now that I've memorised most common tailwind classes, I'm also moving faster than with pure css.

Main downside is that it's annoying having to modify tailwind's config file to add non-default variations (mostly different heights/widths than what it ships with).

Maybe something like Girouette[0] would be better.

[0] https://github.com/green-coder/girouette

In this article, we will use Serverless Framework and Docker Desktop to deploy Dart functions to AWS Lambda. If you haven't installed them yet, please complete the installation using the following commands or links.

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.