Data-scientist who loves to use #datascienceforgood, especially in ecology, energy and the environment. Bonsai, gardening, bikes and music when I'm not at a keyboard.
What's your experience with Dynamo DB? As far as I've heard it it's great for record based transactions, but tricky for aggregate analytics work. (Disclaimer: I've barely even read the docs :p)
Dynamo DB is great nowadays....a year ago was the worst thing I could have used ....I've never written so much code for such a small project (extremely high traffic) to handle just throttling strategies. Then one day we turned on "on demand" and never cared for that service ever again
Data-scientist who loves to use #datascienceforgood, especially in ecology, energy and the environment. Bonsai, gardening, bikes and music when I'm not at a keyboard.
I don't, I guess ;) We used lambda since quite early days but in almost every case we regretted it in the end. It always turned out that Kubernetes with some application processing (eg. Sidekiq) scales better, performs better and we have better insight into what's going on if something goes wrong.
I'm a big fan of what folks have dubbed the GoLD stack:
Who doesn't love a little bit of serverless :D
It almost feels like they purposely picked Lambda and DynamoDB for working with Go, just so the stack would sound that well xddd
Lol yeah
Step one is always have a kick-ass name! :D
Hahah, I'm currently working on a MERN stack, I'm thinking to switch out React to Vue just so I could be the mighty VENoM dev xddd
What's your experience with Dynamo DB? As far as I've heard it it's great for record based transactions, but tricky for aggregate analytics work. (Disclaimer: I've barely even read the docs :p)
Dynamo DB is great nowadays....a year ago was the worst thing I could have used ....I've never written so much code for such a small project (extremely high traffic) to handle just throttling strategies. Then one day we turned on "on demand" and never cared for that service ever again
I have never used it personally for analytics, but I have heard using it in tandem with Amazon Athena is great for that kind of stuff!
I like DynamoDB a lot, though I have heard it's not great if you have a data set which is growing rapidly.
I have used Athena with an S3 data store. That worked well for that particular job :)
I don't, I guess ;) We used lambda since quite early days but in almost every case we regretted it in the end. It always turned out that Kubernetes with some application processing (eg. Sidekiq) scales better, performs better and we have better insight into what's going on if something goes wrong.
Hahah yes, definitely there are draw backs when it comes to serverless, I think it's all about the project at the end of the day.
Your final point is the most important to me, transparency is actually key for when (not if) something goes wrong :)