aws-codedeploy-agent VS gleam

AWS CodeDeploy is a deployment service that automates application deployments to Amazon EC2 instances, on-premises instances, serverless Lambda functions, or Amazon ECS services. A compute platform is a platform on which CodeDeploy deploys an application. There are three compute platforms:

When we deploy code at Aha! we kick off a number of AWS CodeDeploy tasks running in parallel. Here's some code to simulate deployment:

AWS has a service named CodeDeploy for this. It does exactly what you describe.

AWS CodeDeploy is a fully managed deployment service that automates software deployments to various compute services, such as Amazon Elastic Compute Cloud (EC2), Amazon Elastic Container Service (ECS), AWS Lambda, and your on-premises servers.

AWS's developer suite of products includes the AWS CodeDeploy offering, which can help developers deploy AWS Lambda functions and other compute-related services.

Documentation

AWS? Dude, use CodeDeploy green blue with hooks.

AWS CodeDeploy is a service from Amazon Web Services that automates deployments to any instance. It works with any language, platform, or application. AWS CodeDeploy makes it easier to release new features quickly, avoid downtime during application deployment, and handle the complexity of updating applications. Users can also test and track deployments so they're not left guessing or digging through logs when something goes wrong. Our integration with AWS CodeDeploy can be integrated directly into your CI/CD pipeline to improve your AWS DevOps security.

If you have a BFF, that means you have a front-end. If you have a front-end, you gotta host it somewhere. Amplify is an AWS managed service built for hosting Single Page Applications. It abstracts away all the existing serverless tech you’d traditionally use on AWS into a single place, automating most of it. S3 static asses, cache busting on deploy, and it even abstracts it’s own build pipeline using CodeDeploy sourced right from your code repository. Like AppSync, it creates a CloudFront distribution for you, and optionally provides automatic Route53 creation if you want at full URL.

Once a fresh build passes via CodePipeline, CodeDeploy distributes the functioning package to each instance based on your predefined settings. This makes it easy to coordinate builds and upgrade or patch simultaneously. CodeDeploy is code-agnostic and includes typical old code with ease. Every deployment instance can be readily monitored using the AWS Management Console, and any mistakes or issues may be rolled back through the graphical user interface.

I haven't had time to really try to write anything in it, but https://gleam.run/ looks really good too. Like Elm for backend + frontend!

Want a friendly language for building safe systems at scale? Gleam is here for you. It features modern and familiar syntax, that's reliable and scalable. Gleam runs on an Erlang virtual machine, and can run plenty of concurrent tasks. It comes with a compiler, build tool, formatter, editor integrations, and package manager all built in so you can get started right away. Congrats to the team on shipping your first major version 🙌.

While I love Clojure, I have to agree about tooling. I recently started using Gleam* and was impressed at how easy it was to get up and running with the CLI tool. I think this is an important part of getting people to adopt a language.

* https://gleam.run/

If you use languages that compile to WASM (such as Gleam https://gleam.run), and can also run Postgres via WASM, then it opens very interesting offline scenarios with codebases which are similar on both the client and the server, for instance.

Recently, Gleam has gained more popularity, and a lot of developers (including me) are learning it. At the time of this writing, it has exceeded 14k stars on GitHub; it grew really fast for the last month.

Oh, strange that github had a date of 2016 on this one: https://github.com/gleam-lang/gleam/issues/2

I was just going by that, though I do remember checking out gleam 5 years ago or so.

Re: macros, I really do think they’re a big deal and all the other newer languages I’ve used, such as Rust have some kind of macros or powerful meta programming features.

For older languages, a few, like Ruby have enough meta programmability to make nice DSLs, but many others don’t. Given the choice, I’d much rather have Elixir/Clojure style macros than other meta-programming facilities I’ve seen so far.

I had been only following this language with some interest, I guess this was born in gitlab not sure if the creator(s) still work there. This is what I'd have wanted golang to be (albeit with GC when you do not have clear lifetimes).

But how would you differentiate yourself from https://gleam.run which can leverage the OTP, I'd be more interested if we can adapt Gleam to graalvm isolates so we can leverage the JVM ecosystem.