klotho VS libaws

Another project in this space is Klotho. I think it's the only one with broad language support so you can write in Go or Python or JavaScript or Java or C#.

https://klo.dev/

I'm one of the creators of Winglang that is featured there as one of the future 4th gen. tool, along with Eventual, Ampt and Klotho.

Hi everyone, we’ve been working on an adaptive architecture engine as part of the open-source Klotho (github), and are now adding an intelligence layer on top of it we call InfraCopilot that features:

Something like this for example: https://klo.dev/

disclaimer: I'm one of the founders

We're building klotho[0] for many of the reasons mentioned here. (happy to answer questions). We transform plain code to cloud native code. The majority of the complexity is moved into the Klotho compiler, and what devs handle is the simplest bundle that's easy to deploy and operate on public clouds using standard tools.

[0] https://github.com/KlothoPlatform/klotho

When I was putting together the pitchdeck for our startup I wanted to search for pitchdeck slides to learn from - but I was looking for specific sections or types of startups for slide decks. To find that one relevant slide, I had to open tens of decks and scroll through them. So I decided to make a tool that would allow me to search inside the decks more easily: SearchTheDeck.com

AWS is heavily invested in its serverless offerings. Every year during re:Invent, they introduce more and more integrations to the already vast toolkit. They know the value serverless brings, specifically for small-to-medium-sized companies. There definitely is a tipping point, where serverless becomes more expensive to run than a more traditional serverful setup, but for most companies, it's at the scale of large enterprises; we're talking a couple of thousand requests per second scale. Tooling is still not perfect but improving every year. Great frameworks, like the serverless framework, chalice and others make it super easy to get up and running with this stack. No need to configure infrastructure details (though I'd always suggest learning the ropes), you can just run a deploy command and you're done. Just to put this into context, even the builders of the Adaptive Architecture (new wave of infrastructure management, e.g. Klotho and Winglang) are prioritizing serverless services on the roadmaps.

i print the error along with file and line number every time i return it. clunky, but it works.

in fact i print file and line with every log message.

https://github.com/nathants/libaws/blob/87fb45b4cae20abd1bb1...

cloud is so good now it’s hard to justify not doing something bespoke. ec2 spot is insanely cheaper than turnkey cicd, and better in almost every way.

i’m delighted to pay 30% over infra cost for convenience, but not 500%. and it better actually be convenient, not just have a good landing page and sales team.

this month i learned localzones have even better spot prices. losangeles-1 is half the spot price of us-west-2.

for a runner, do something like this, but react to an http call instead of a s3 put[1].

for a web ui do something like this[2].

s3, lambda, and ec2 spot are a perfect fit for cicd and a lot more.

1. https://github.com/nathants/libaws/tree/91b1c27fc947e067ed46...

2. https://github.com/nathants/aws-exec/tree/e68769126b5aae0e35...

like linux, cloud is a lot to learn, but worth it.

like linux, cloud is best kept simple, or it can become brittle and confusing.

like linux, cloud has a lot of cool things like zfs, that should be appreciated but rarely used.

like linux, using go makes your life a lot easier. the aws go sdk is the documentation.

like linux, you have to learn a lot and then find the core utility you actually care about. for me it is:

https://github.com/nathants/libaws

the good new is, for the 95% of projects that can tolerate it, aws the good parts are actually both simple and easy[1].

it’s hard to find things you can’t build on s3, dynamo, lambda, and ec2.

if either compliance or a 5% project demand it, complicated solutions should be explored.

1. https://github.com/nathants/libaws

i also wanted a good cli for aws, and built one:

https://github.com/nathants/libaws

companies like fly are fantastic.

they provide a good service, and they put market pressure on aws.

cool transition and fun writeup!

for low, intermittent traffic sites, go on lambda might be a better comparison:

https://github.com/nathants/libaws/tree/master/examples/simp...

lambda + s3. add ec2 spot if you need it.

just make sure you understand how billing works. mostly it’s just egress bandwidth is expensive.

do something like this:

https://github.com/nathants/aws-gocljs

or with less opinions:

https://github.com/nathants/libaws/tree/master/examples/simp...

welcome to cloud, glhf!

aws ux for retaining both hair and sanity.

https://github.com/nathants/libaws

build and scale systems with artificial load on aws! scaling the load testing will be just as interesting as scaling the system under test.

start with low bottlenecks, ie a cluster of c6i.large ec2 spot. how fast can you do this? have fast can you scale that? ec2 and s3 is all you need to build anything.

use ec2 spot, avoid network egress, avoid cross region/zone traffic, create and destroy ec2 instances as needed instead of letting them sit idle. you could grow system scaling intution for the price of your streaming subscriptions.

start with something like this:

https://github.com/nathants/libaws/tree/master/examples/comp...

maybe mess around with public datasets on aws, just make sure to be in the correct region to avoid data egress.

welcome systems friend. one accurate measurement is worth a thousand expert opinions. scaling is fun!

aws has too many knobs, presumably to satisfy the union of the needs of all the enterprise customers. that said, lambda+s3+dynamodb+ec2 are pretty good once you tape over all the knobs that aren't needed. i work with them like this[1].

these days i build on aws and r2. aws for the nuts and bolts, r2 for high bandwidth egress. it's a perfect match.

1. https://github.com/nathants/libaws