I fixed https://schizo.social's auth; had to index my #dynamoDB with a composite primary key (#aws is an art)
I'm a bit stumped about what to work on next.
The load time for the timelines bothers me; it's still occasionally timing out just loading 20 toots from two servers. I feel like introducing a #webSocket is my only choice, but I don't like the idea of adding client-side rendering.
#client #Mastodon #programming #webdev #websocket #aws #dynamodb
Is #CouchDB still lovable? Going through the docs right now. Seems more fun than using a corporate (and proprietary) Document DB like #MongoDB, #DynamoDB or #Firebase. Also looks more fun than using the weird JSON syntax of #PostgreSQL.
#couchdb #MongoDB #dynamodb #firebase #PostgreSQL
DB-Engines Ranking climbers of the month:
1. #DynamoDB
2. #SnowflakeDB
3. #Databricks
https://db-engines.com/en/ranking
#dynamodb #snowflakedb #databricks
@licked testing is plenty helpful! I have lots of options; https://arc.codes supports #dynamoDB, and webSockets. I'm just trying to keep it as simple as I can, so I'm being conservative. I made the repo public if you want to have a look; https://github.com/jessehattabaugh/schizo-social
Preview: AWS .NET Distributed Cache Provider for DynamoDB
https://aws.amazon.com/blogs/developer/introducing-the-aws-net-distributed-cache-provider-for-dynamodb-preview/
This library enables Amazon DynamoDB to be used as the storage for ASP.NET Core’s distributed cache framework. A cache can improve the performance of an application; an external cache allows the data to be shared across application servers and helps to avoid cache misses when the application is restarted or redeployed.
#AWS #DotNET #DynamoDB
https://cacm.acm.org/magazines/2023/6/273229-foundationdb-a-distributed-key-value-store/fulltext — strangely similar to the internals of #dynamodb and invented at about the same time.
FoundationDB is the “metastore” used on Snowflake. It is also used internally at Apple in projects they don’t disclose.. . it sounds like a cool system, too hyperscale for me to use right now..
In a universe where #cockroachdb cross-breeds w/ foundationDB we would get a really amazing open source distributed DB.
Just learned that we can do CRUD operations to DynamoDB directly from API Gateway! My mind is blown. Has anyone here actually implemented that? I’m wondering if this is a “just because you can, doesn’t mean you should” scenario.
Just released my first ever blog post 🎉 . Deno released a new globally distributed database, KV, so I went down the rabbit hole comparing it to other globally distributed databases.
https://global-db-comparison.deno.dev/
#serverless #deno #DenoKV #PlanetScale #Fauna #DynamoDB #Upstash
#serverless #deno #denokv #planetscale #fauna #dynamodb #upstash
#Amazon #DynamoDB has come a long way since its launch in 2012!
Akshat Vig presents his experience of operating this system at a massive scale and how the architecture continues to evolve to meet the ever-increasing demands of customer workloads.
Don't miss this #InfoQ insightful talk: https://bit.ly/3NkpMgf
Sharing the blog post I wrote about creating our #cli in #rust:
https://grafbase.com/blog/how-we-built-the-grafbase-cli-in-rust
#rustlang #sqlite #wasm #webassembly #dynamodb #cloudflare #graphql
#cli #rust #rustlang #sqlite #wasm #webassembly #dynamodb #cloudflare #graphql
唯一無二!!サーバーレスメモリキャッシュサービス Momentoから Momento Web SDK が登場!
https://qiita.com/yoshii0110/items/dc26e9b4b0cfc05c421b?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#DynamoDB #フロントエンド #serverless #momento #インメモリキャッシュ
#dynamodb #フロントエンド #serverless #momento #インメモリキャッシュ
#DynamoDB also rewards access patterns that pull a range of values under a single partition key, and modyne helps to leverage that fact with strongly-typed `Aggregate`s and `ProjectionSet`s, greatly simplifying the process of consuming queries containing mixed entities.
Modyne stands on the shoulders of `serde_dynamo` and `serde` to provide serialization and deserialization support.
Modyne provides a high-level API to define entities with the goal of guiding usage toward a "pit of success". Usage centers on entities defined using the `EntityDef` derive macro and `Entity` trait, declaring the primary and index keys that the entity participates in. From there, persisting the entity is as simple as `my_entity.create().execute(&table).await?`. This makes the experience in usage somewhat similar to an ORM.
Single-table design is a method of building a data model that takes advantage of the strengths of #DynamoDB and its architecture to ensure fast and consistent operation. This model was popularized by Alex DeBrie in his book "The DynamoDB Book".
Announcing the release of modyne, a new #rust crate for building data models with AWS #DynamoDB, particularly when following single-table design principles. 🧵
TL;DR: Check out the docs at https://docs.rs/modyne
Is there any interest in me open-sourcing this? I have a couple of other open-source projects already, including aliri, aliri_braid, protoc-gen-prost, as well as being an every-so-often contributor to prost, tonic, and several other Rust projects. I don’t want to “add” to my maintainer burden unnecessarily, but if there’s interest in such a library, I can make it public. Thoughts?
After doing some significant work with DynamoDB and getting introduced to “single-table design” as defined in Alex DeBrie’s “The DynamoDB Book”, I’m getting pretty close to finishing up a high-level Rust crate to make interacting with DynamoDB easier, less error-prone, and a smidge more ORM-like, all while being opinionated and leaning heavily into the single-table model. It builds on the aws-sdk and the great work in serde_dynamo. 🧵
イラストで理解するDynamoDBのテーブル
https://qiita.com/Yona_Sou/items/caf1d2ac5867ed0c3154?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#AWS #DynamoDB
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/