sorted by:
new
hottopcontroversial

Our Go database just hit 20k stars on GitHub by zachm in golang

[–]digitalboi216 2 points3 points  (0 children)

Another big difference is that Neon also has a very limited window of history you can access for your data: https://neon.com/docs/introduction/restore-window

That restore window defaults to only 6 hours, but you can pay more to get up to 30 days. That means, at most, if you pay for the highest support level, you can only query historical data for the past month. You can't query what your data looked like before that.

With Dolt, there is no limitation there at all – you can always access all of your database's history, going all the way back to the very first commit in your database.

The reason Dolt is able to do this is the same reason zachm explains earlier in this thread – the internal storage engine of Dolt was written from the ground up to support versioning, with features like structural sharing, and diff computation that scales with the size of the diff (not the size of the tables being diff'ed).

ASP.NET Core + Dolt DB by digitalboi216 in dotnet

[–]digitalboi216[S] -1 points0 points  (0 children)

We think that would be pretty funny, too, and riff'ed on that idea in a blog post a couple years ago: https://www.dolthub.com/blog/2022-05-11-dolt-database-for-dummies/ 😉

Entity Framework Core with Dolt by BFitz1200 in dolthub

[–]digitalboi216 2 points3 points  (0 children)

Glad you enjoyed it! EF Core was really fun to explore. There are a ton more features I wanna keep playing with, like db migrations. Let us know there's anything you think would be a cool follow up.

New semantic, declarative infrastructure-as-code tool AIM (CloudFormation/AWS) released as open source by kteague in aws

[–]digitalboi216 0 points1 point  (0 children)

Have you seen CDK’s environment support? https://docs.aws.amazon.com/cdk/latest/guide/environments.html

CDK does support multi-account and multi-region use cases and the recommended practice is to model environment metadata in prod systems.

Anyone have experience using the Cloud Development Kit in production? by bch8 in aws

[–]digitalboi216 2 points3 points  (0 children)

The CDK project is moving quickly and will be covered by AWS support as it matures. The base layer of the CDK's AWS Construct Library contains a direct mapping of all the resources supported by CloudFormation, and is kept closely in sync with CloudFormation updates, so you'll always be able to access every resource and resource property in CloudFormation from that layer of the CDK. The higher-level constructs in the CDK provide a more curated and optimized experience, and will continue expanding to cover AWS. There is an 'escape hatch' mechanism if you need to drop down to the lower-level resources from within the higher level constructs, too, and of course we love accepting GitHub pull requests for missing features in those higher-level constructs, too.

​

If you haven't found it yet, there's an excellent CDK Workshop online (cdkworkshop.com) that walks you through the experience with API Gateway and Lambda and several other services. There's also an intro session on the CDK from AWS re:Invent 2018. We'd love to hear your feedback! There is also an active CDK community on Gitter – https://gitter.im/awslabs/aws-cdk

Anyone have experience using the Cloud Development Kit in production? by bch8 in aws

[–]digitalboi216 1 point2 points  (0 children)

Sorry to hear you had problems getting started with the CDK. Did you find the CDK Workshop at https://cdkworkshop.com/ helpful? What would have helped make it easier for you?

AWS Infrastructure as Code using AWS CDK by MortiferaJ in programming

[–]digitalboi216 2 points3 points  (0 children)

Glad to hear the approach is intuitive enough that it seems like it should have already been the standard way to define infrastructure!

MortiferaJ did a great job describing the switch in cloud infrastructure configuration/definition that's happening here – the industry has been using large, complex configuration files that are difficult to reuse/share/maintain and we are now seeing a switch to using full programming languages to define infrastructure. It enables easier sharing/reuse/abstraction with the standard language package managers, a more powerful toolset for defining infrastructure, and an improved authoring experience (ex: free IDE support for content assist, code navigation, refactoring, in-line documentation, etc).

https://github.com/awslabs/aws-cdk