Recherches récentes
Options de recherche
#dynamodb
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. 
@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.
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/
Excited to share my recent presentation on Serverless and Swift at the @NSLondonMeetup! 
If you're into #Serverless development or #Swift, you won't want to miss it. Watch the video!
https://www.youtube.com/watch?v=D4qSv_fhQIo
#Breeze #ServerSideSwift #AWS #Lambda #DynamoDB #APIGateway #iOS
Gonna do a pass with #golang. It can do serverless on #aws if I want to, but will start on a VPC.
Also local #Postgresql and if I get tired of that I can go with #Dynamodb
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.
#Breeze is now on Swift Package Index
! 
Check it out!
https://github.com/swift-sprinter/Breeze
Serverless API in Swift, 1 line of code! Blazing fast!
️
#AWS #Serverless #Lambda #DynamoDB #APIGateway #Swift #ServerSideSwift #SLS #FullStackSwift
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
One of the more prominent trends in 2022 was the migration to more serverless-based architectures. From #Lambdas to Fargate to #DynamoDB, we saw it all. But what is a #serverless architecture? #dotnet #devops
Serverless architecture is a software architecture that allows developers to build and run applications and services without worrying about the underlying infrastructure. It is characterized by a pay-per-use model, with the infrastructure provided by a cloud provider on demand.
At the moment, our team consists of me and Kevin. Kevin is a Stanford Law School-educated lawyer turned coder with experience working in Mergers & Acquisitions at Simpson Thatcher, and also as a software engineer at #LinkedIn. I studied computer science at the University of Michigan and worked as a senior software engineer at LinkedIn prior to founding Version Story. We’re backed by investors including Y Combinator and Accel Ventures.
We’re looking for a strong, generalist engineer who is interested in traversing all parts of the stack to build new features, architecting our infrastructure, and helping us design git for documents.
Responsibilities
As a founding engineer, we'd expect you to,
Ship and own features.
Assist in designing scalable architecture for our platform.
Establish design patterns, style conventions, and other habits to set the tone of our engineering culture as we scale.
Talk to customers.
Qualifications
3+ years of work experience.
You are a clear and effective communicator.
You are intellectually curious.
You are creative and are eager to contribute your ideas to our engineering strategy, product vision, etc.
Bonus points if you have experience in the following technologies. Experience is not required, however, so long as you're willing to learn:
#Python + #Flask
#TypeScript + #React
#Java
#AWS - S3, #DynamoDB, #Elastic #Beanstalk, #Lambda
Serverless Framework
I’ve published a new post on Bedrock’s tech blog, based on what we’ve done for the last 3-4 years! #FinOps
« How many #AWS #DynamoDB RCU and WCU should we reserve to achieve maximum cost reductions, when our workloads are changing all the time? »
https://tech.bedrockstreaming.com/2022/11/22/dynamodb-reservations.html
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.