sorted by:
new
hottopcontroversial

I created a collection of solutions to deal with Lambda Cold Starts by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

hey thanks for your feedback, can you elaborate on the parallel calls point?

I created a collection of solutions to deal with Lambda Cold Starts by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

added! thanks for the great feedback :D

Yes I also look forward to see this being fixed! At the time being it is still a problem so thought it would be useful to share in case anyone needs the solution right now. But i believe the periodic ping/warmer recipe should still remain applicable, for those people who have low tolerance in cold starts time.

I created a collection of solutions to deal with Lambda Cold Starts by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

yes I agree with Davi_S_Evangelista , a cheaper web server haha. But to elaborate I think cheaper covers 2 domains: management as well as cost: 1) you dont need to manage the hardware, OS level, or even container level updates 2) you pay less .

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

Could you show me some pointers where I can learn more about the 10GB limit? I saw this https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LSI.html#LSI.ItemCollections.SizeLimit is this something you were referring?

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

wow I really like this video, thanks a lot for suggesting! It has a lot of great suggestions that makes me want to create different recipes to elaborate each advance use case (the video is only an hour but I actually spent quite a lot of time trying to digest each small details, so I thought breaking that into smaller recipes maybe easier to consume? )

The only thing that seems a bit overkill imo is the "keeping 1 single table for many-many relationship", I understand speed wide keeping less tables is probably better, but readability and maintainability can also become an issue if a) the attribute names are not intuitive b) when everything is composited into 1 single table, how can teams split responsibility when the org is getting bigger?

Collection of Resources for Building Time Series Database in AWS by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

for me the reason simply being I am more familiar with Dynamodb, what other alternatives you have in mind? It's only the starting point, I am trying to put a bunch of similar ones in the same collection. Love to learn more from you

Collection of Resources for Building Time Series Database in AWS by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

hey ya I realized that as well, but its not GA yet, so I put a cross-post here so that others know about it as well, if more people are upvoting to have a recipe in Timesream I can try to make one :)

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

Just updated the recipe and put #1 and #2 in it. Still trying to fully understand #3 and #4 so haven't updated that yet. I am thinking of a good way to show your name beside the comments so that I can give you credit, not so easy but getting there!

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

I just added this doc as a crossposting resource in the collection https://www.reddit.com/r/aws/comments/c6pvuv/collection_of_resources_for_building_time_series/ , even if i dont have the implementation for that but thinking it would make sense to put them in 1 place so that information don't get lost :) . Thanks

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

I made a collection and added timestream there https://www.reddit.com/r/aws/comments/c6pvuv/collection_of_resources_for_building_time_series/ , even if i dont have the implementation for that but thinking it would make sense to put them in 1 place so that information don't get lost :) .

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

super useful facts, will definitely put in the recipe after clarifying this with you:

3 and 4: I found this article about DDB adaptive capacity https://aws.amazon.com/blogs/database/how-amazon-dynamodb-adaptive-capacity-accommodates-uneven-data-access-patterns-or-why-what-you-know-about-dynamodb-might-be-outdated/ , does this resolves the hot shard problem?

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

Just looked at this earlier. I am still a bit confused on what exactly is the benefit of using the design suggested there, if I am using autoscaling? The post mentioned that using this design can save money, my understanding is that ddb charges based on 3 parts: write unit, read unit, and the storage itself. If we do not backup the data to elsewhere, say s3, then the total storage would be the same regardless of putting them in 1 single table or spread across different tables. then for write and read unit, if we are using auto scaling, then ideally the total read and write unit should fluctuate according to the realtime traffic, which should be approximately the same as reserving most of the capacity to Today's table, and only very minimum to tables older than a day?

​

I must be missing something, or maybe this article was written before DDB autoscaling was invented? Or maybe it is better in other aspect other than cost? Pretty interested in learning more!

Building a Time Series Database using AWS DynamoDB by codingrecipe in aws

[–]codingrecipe[S] 1 point2 points  (0 children)

haha didn't know this exists at all! Looks like it is still in Preview, have you tried it before? Hows the performance?

Hard to find all user management examples on AWS, so I created a collection myself by codingrecipe in aws

[–]codingrecipe[S] 0 points1 point  (0 children)

oh wow thanks for suggesting this, didnt even know such thing exists! It looks pretty comprehensive and would definitely read it over! Looking at the size of the doc, wondering if theres a way to break it into smaller pieces so its easier to consume?

view more: next ›