How to build #MongoDB Event Store? The neat part is you don't!

Oh well, past me thought like that, but Alexander Lay-Calvert persuaded me to change my mind and did most of the work. We delivered #MongoDB storage, and it went surprisingly well. I wrote a detailed write-up on how to do it!

There were many interesting challenges in how to make it consistent and performant, so I think that's an interesting read.

I think it's a good guide if you're considering using #MongoDB as anevent store. Surprisingly, I have had numerous discussions recently with people trying to do it.

If you're considering using key-value databases like #DynamoDB and #CosmosDB, then this article can also outline the challenges and solutions.

My first choice is still on #PostgreSQL, but I'm happy with the #MongoDB implementation in #Emmett.

If #MongoDB is already part of your tech stack and the outlined article constraints are not deal-breakers, this approach can deliver a pragmatic, production-friendly solution that balances performance, simplicity, and developer familiarity.

I'm not sure what took longer, delivering the implementation or writing this article. So I'll appreciate the feedback and sharing with your friends.

https://event-driven.io/en/mongodb_event_store/

holy fk, aws just cut dynamodb pricing by >50%

https://aws.amazon.com/blogs/database/new-amazon-dynamodb-lowers-pricing-for-on-demand-throughput-and-global-tables/

@GossiTheDog Ultimately - this is a big part of why I hate the very-cloud-specific (and normally proprietary tech) like #DynamoDB. You can get a framework figured out to migrate most of your Lambda-ey code back on prem* (containerizing, building a scheduler of sorts etc), you can obviously EC2 on prem*, you can RDS and S3 on prem*, but there's those cloud-specific things that leave you beholden to ol' Jeff Bezos. The inflexibility to move is what scares me.

* or to another cloud

I open sourced a thing for aggregation of DMARC reports from multiple domains.

https://codeberg.org/falken/dmarc-report

cool, deep, in depth article about Github upgrading MySQL is full of reasons why I personally choose to use #DynamoDB

https://github.blog/2023-12-07-upgrading-github-com-to-mysql-8-0/

Feels like #DynamoDB is having a moment. Perception is shifting positively as people learn aesthetics are not a great way to judge a database. Semantics are.

We benchmarked read and update performance by running common workloads with a fixed dataset size of 50GB (plus replications) and multiple throughput levels (measured by operations per second) across two popular SDBaaS solutions: Amazon #DynamoDB and #Redis Enterprise Cloud. No matter which workload we tested, Redis Enterprise Cloud maintained an end-to-end latency of 0.5-0.6 msec.
https://redis.com/blog/serverless-databases-as-a-service/

your regular reminder that #dynamodb is perfectly capable of modelling relational data

https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-relational-modeling.html

It seems like it should be possible to make a super lightweight #ActivityPub (Mastodon compatible) server that is #serverless, and e.g. stores all its state in a light serverless database like #DynamoDB.

Then you would get free scaling to multiple users, very low ongoing costs, and you could even use a premade ActivityPub client as your frontend. Is there an open source initiative along these lines already?

I realise I'm likely underestimating the effort involved here.

#introduction

Hi, I'm Erik, a #golang programmer from Norway.

I'm all for using #statecharts, so much so that I made https://statecharts.dev. I have witnessed the rise and fall of #rest, but continue to support restful architecture. I think I'm somehow naturally drawn towards #declarative systems.

Heavily into #kubernetes, #openshift, #kubebuilder professionally (at my employer Stibo DX), and have a sprinkle of #awslambda / #dynamodb in some personal projects.