awesome-go-storage VS containers-roadmap

Awesome Go Storage (GitHub)

Any many many more. Check https://github.com/gostor/awesome-go-storage

C is significantly slower at concurrency when implemented naively. It's as fast as languages like Go when implemented using the same techniques, which is not obvious and trivial to use like in a higher level GC'd language. GC actually helps out a ton there, for example look at the complexity of async/await in Rust which requires the notion of pinning.

https://github.com/gostor/awesome-go-storage#database

https://java-source.net/open-source/database-engines

Not a database but honorable mention, LMAX disrupter: https://lmax-exchange.github.io/disruptor/

You may want to start from here: awesome-go-storage and choose what fit your needs

This is neat! I am quite a fan of all the go based file systems that are springing up. Question: what are the main compare and contrast points between juice and seaweed fs?

Here is a compendium for those interested:

https://github.com/gostor/awesome-go-storage

Thanks for showing up and answering questions. Congratulations on the release.

What kind of plans for support of Rust's evolving async ecosystem?

Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1

Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically

Second, We will only rely on one managed node group, but we will leverage Karpenter; however, karpenter needs to be deployed on a node. (This may change soon once the Karpenter is available on the EKS Control Plane.) [EKS] Karpenter inside control plane · Issue #1792 · aws/containers-roadmap

As written in the AWS documentation, during periods of extremely high demand, Fargate Spot capacity might be unavailable. In concrete terms, if your ECS service is set up to execute tasks in 100% Spot, there is a risk of running out of capacity. A workaround has been created in the hope that one day this issue will be implemented by the AWS team. This workaround allows you to set up two ECS services :

Deploying Fargate with CDK has to have been the most pleasant developer experience I have ever had with any product so far.

If image caching becomes a reality with Fargate I can't imagine a need to ever use anything else

https://github.com/aws/containers-roadmap/issues/696

Eks Fargate doesn't support spot yet https://github.com/aws/containers-roadmap/issues/622

Until podman could be used with AWS ECR/ECS it's pretty much moot in my case: https://github.com/aws/containers-roadmap/issues/626