How is this lakehouse, its still same architecture with data lake and data warehouse and etl performed??
@twiggedtoday3 жыл бұрын
Very useful presentation !!
@MrSravan843 ай бұрын
The data rate of FAA Swim Data is 5000 rec per minute and is that considered massive ? or I misheard it ?
@ramkundala49253 жыл бұрын
Great presentation
@unitycatalog2 жыл бұрын
What are the latencies one gets when using EMR for real time ?
@namhoanghoai97503 жыл бұрын
I really like the Aviation Case, which is as similar as what I am dealing with now. Hope to get a connection with presenters for a further advice
@unitycatalog2 жыл бұрын
Not one line on what is "lake house" You can use this that bla, but what exactly is the service or entity you call lake house
@CloudNativeJanitor Жыл бұрын
its a collection of services, think of it as a pattern, main components would be a data lake (most likely based on s3) and data warehouse ( e.g. Redshift) and if you consider goverance, security, lakeformations, but there are many other options and extensions I guess, e.g. visualizations can be handled by quicksight or AMG
@steveb76002 жыл бұрын
Pretty sure there is no connector between Grafana and DynamoDB as shown in your diagram. You are gonna need a third party connector $$ for that.
@dbatexas2 жыл бұрын
why not talk about data lineage ? data quality ? it is also a big issue with data silos
@CloudNativeJanitor Жыл бұрын
they did cover it briefly using lake formations
@gobindamohan2 жыл бұрын
Most unhelpful video ever.
@nithints302 Жыл бұрын
Lakehouse.. Where is lakehouse here.. All blah blah
@awssupport Жыл бұрын
Sorry to hear about this trouble. You can take a look at this article with some info about Lake House that may assist: go.aws/3ZmLdSc. 🏗️ If you have any additional questions, our experts over at re:Post platform can weigh in & share their knowledge: go.aws/aws-repost. 🎓 ^AK