I've come to the conclusion that I don't need #DynamoDB at all - and instead need a document store like Mongo.
There are so many weird limitations with Dynamo, that I don't think it fits my use case.
I also think I can do a lot with some signed JWT's too
I was right, #DynamoDB might be right for what I'm doing, but you _really_ need to understand how you're going to query this table up front.
So easy to paint yourself into a corner
Absolutely loving these AWS + TUI tools 
️ **ddv**: Terminal DynamoDB Viewer
Supports view, search, update & delete operations
Efficiently handles large tables for querying or updating
Written in Rust & built with @ratatui_rs
I've developed a simple to use DynamoDB ODM for PHP. Inspired by the likes of Doctrine, this ODM provides a powerful and flexible approach to the mapping DynamoDB items to PHP objects, making use of the attributes to provide mappings and transformers.
Feedback is always welcome, so please have let us know how you find it or if you have any questions. Usage examples are in the Readme.
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. 
This 3-part series about #DynamoDB is pretty amazing. Especially benchmarks showing how poor choice of partitioning keys theoretically leads to the limit of 6k RPS. But, after several minutes, DynamoDB repartitions your data to reach 100k+ RPS. With <2ms latency: https://aws.amazon.com/blogs/database/part-2-scaling-dynamodb-how-partitions-hot-keys-and-split-for-heat-impact-performance/
Supercharge your applications with DynamoDB Streams! This video dives into leveraging change data capture, configuring the AWS SDK, and handling stream events. Unlock asynchronous power: #programming #DynamoDB #AWSLambda https://youtu.be/Yqnci1XEKkM
https://youtu.be/Yqnci1XEKkM
#LocalStack 3.7 Released: Local #AWS Emulator
• 
Emulates 50+ #AWS services locally (#Lambda, #S3, #DynamoDB, #Kinesis, #SQS, #SNS, more)
• 
Runs in a single #Docker container on your machine or #CI environment
• 
Enables local #CloudDevelopment without connecting to remote cloud
• 
Ideal for testing complex #CDK applications or #Terraform configurations
• 
Supports additional features like #CloudDevelopment workflows
• 
Open-source version available, with extended Pro version
#LocalStack provides a comprehensive local #AWS environment for developers and testers, simplifying cloud application development and reducing costs. Compatible with various deployment methods including CLI, Docker, and Helm.
TIL records with the same partition key may be located on different partitions in #DynamoDB. The process is called "split for heat" where records are split at some threshold of sort key. This doesn't work if there's Local Secondary Index: https://aws.amazon.com/blogs/database/part-2-scaling-dynamodb-how-partitions-hot-keys-and-split-for-heat-impact-performance/
I find it funny that the official #AWS #DynamoDB local mock is a #Java wrapper around #SQLite :-) https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.DownloadingAndRunning.html
Registration form is working, and I even wrote a #Playwright test to check it!
I started moving the fetching logic to a queue, and I've got it wired up, but the next step is to make the queue handler save the user's achievements to the DB as well.
This is where #DynamoDB trips me up. There are Achievements, there are Users, and then there are Achievements that a User has earned; a many-to-many relationship. I'd feel pretty confident in how to design an SQL schema, but not #NoSQL
I've used the #RetroAchievements API to fetch my achievements. Now I need to create a form so that other people can register, and move the fetching logic to an event queue.
I'm using #Architect/@enhance_dev@fosstodon.org again cause I'm hooked on that #AWS #serverless #devops.
So I'll store people's RA username/apikey in #DynamoDB then have a scheduled event that loads all the keys that need to be updated on a regular basis.
I'm in the process of writing my own email service. Hoping to start extracting myself from the Google ecosystem one service at a time, and when it comes to email I really want to roll my own.
Since I'm a team of one, I've had to consider how I'd get this done in a reasonable timeframe. I ended up deciding to go with AWS and have been able to quickly setup a way to send and receive email on my domain. I decided to have AWS write the email directly to S3, and now I'm writing a job to parse the files, upload to DynamoDB, and then move the file to a sub folder based on the recipient.
Next I'll be working on the web app to manage the emails in DynamoDB. I'll end up needing to write a simple login system, setup https, and then I can start working on the meat of the project.
While you learn the basics of Rust, AWS Lambda, #SAM, #DynamoDB, and #API Gateway, you'll also build a fully functional URL shortener that you can deploy in your AWS account and experiment with!
For those who have already purchased a previous version, you can download the new release directly from the product page on Gumroad. 
If you’re intrigued and considering buying the book now, visit our website for all the details.
Today is DBA Appreciation Day!
If you have a DBA in your company who relentlessly takes care that your databases are humming along and delivering query results, today is the day to say Thank You!
#PostgreSQL #MySQL #MariaDB #Oracle #Greenplum #SQLite #SQLServer #MongoDB #Redis #Snowflake #DB2 #Elasticsearch #Teradata #InfluxDB #Firebird #Informix #Couchbase #CouchDB #Vertica #DuckDB #CockroachDB #SAPHana #Splunk #DynamoDB #BigQuery #Hive #Neo4j ...
What's faster? #Amazon #Prime package delivery or #AWS #DynamoDB auto-deleting expired records?
"Items with valid, expired TTL attributes may be deleted by the system at any time, typically within a few days of their expiration"
Typically. A. Few. Days. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html
@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
@sanderbol I was looking for an open-source database. Amazon DynamoDB is a proprietary database.
GitHub: 
