View profile

SF Data Weekly - Why 191, Mini-Big at Home and Orbit

May 21 · Issue #190 · View online
SF Data Weekly
If you’ve ever wondered why 191 or 255 became default text field sizes in databases – and who hasn’t – our pick has the story.
We also have a piece on setting up a mini-big data environment at home, and Uber’s new time-series forecasting tool, Orbit. Stay healthy!

Our Pick
Grouparoo Blog: Why do database columns have a character length of 191?
Data Pipelines
Creating Data Lake using AWS S3, Glue, and Athena | by SHUBHAM KAUSHIK | May, 2021 | Dev Genius
Advanced ETL that meets your security and regulatory needs
Data Storage
Setting Up a Mini Big-Data Infrastructure at Home | by xddd | May, 2021 | Medium
Introducing Cold Storage for Amazon Elasticsearch Service | Amazon Web Services
Data Analysis
Productivity Tracking with the Notion API and Python | by Lucas Soares | May, 2021 | Towards Data Science
Data Visualization
Interpreting data visualizations- III | by Bilwa Gaonker | TheLeanProgrammer | May, 2021 | Medium
Power BI — The tool that is beating Excel | by Octavio Bomfim Santiago | May, 2021 | Towards Data Science
Data-driven Products
Introducing Orbit, An Open Source Package for Time Series Inference and Forecasting | Uber Engineering Blog
LyftLearn: ML Model Training Infrastructure built on Kubernetes | by Vinay Kakade | May, 2021 | Lyft Engineering
Data Engineering Jobs
Did you enjoy this issue?
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue
650 California St., San Francisco, CA 94108