Erik on Software

Sign in Subscribe

Topic

architecture

A collection of 128 issues

Community Comment: Part 34 - Popular data engines use Java / the JVM because it ruled the enterprise for many years

* Reasoning behind popular data engines & Java * Java / the JVM long ruled the enterprise * Spark, Flink, Presto & Trino are all Java-based * Remember: Presto & Trino share some history The comments I provided in reaction to a community discussion thread. Head of Product at Data Lakehouse Product Firm: 🤷‍♂️ GitHub PRs

Community Post: Part 3 - Delta Lake 3.0 is like an electric car charging standard

* The power of open source * Delta Lake 3.0 is just one example * Parquet-based data lakehouse file format * Similar to electric car charging standard A well-received community post I recently made: https://www.linkedin.com/posts/erikgfesser_snowflake-deltalake-iceberg-activity-7080482215016476672-Xrh0 Just over two months ago in mid-April of this year, I couldn&

Community Comment: Part 30 - With respect to Azure, Databricks Unity Catalog & Microsoft Purview is not an either-or proposition

* Databricks Unity Catalog & Microsoft Purview * Not an either-or proposition for Azure * Likely need to integrate these products * Integration dependant on several factors The comments I provided in reaction to a community discussion thread. Cloud Solutions Architect at Consulting Firm: Read my latest post if you want to know what

Community Comment: Part 28 - Technical debt is actually a subset of organizational debt

* Not all technical debt is the same * Discussion with purported CTOs * Technical debt is subset of organizational debt * Business + technology = "our business" The comments I provided in reaction to a community discussion thread. Fractional CTO and "Engineering Management Expert": "Technical debt? Is that a joke?

Community Comment: Part 27 - Assessment is needed when deciding between transactional and analytical modeling

* Transactional versus analytical modeling * Discussion with purported staff data engineer * Making broad generalizations doesn't help * Quoting $ savings in vacuum not advised The comments I provided in reaction to a community discussion thread. Owner of Data Engineering Training Firm and former Staff Data Engineer at Airbnb: If you model

Media Query Source: Part 45 - Reworked (US digital magazine); OpenAI & the Databricks-Microsoft AI alliance

* Reworked (US digital magazine) * OpenAI & the Databricks-Microsoft AI alliance * Databricks available on AWS, Azure & GCP * Microsoft providing AI options makes sense My responses ended up being included in an article at Reworked (September 7, 2023). Extent of verbatim quote highlighted in orange, paraphrased quote highlighted in gray. Above

Media Query Source: Part 43 - CNBC (US business news television channel); Benefits of using self-service analytics tools

* CNBC (US business news television channel) * Benefits of using self-service analytics tools * Timely, custom exploratory analyses enabled * Appropriate data governance needed The responses I provided to a media outlet on March 3, 2023: Media: I'm working on an article about the benefits of using self-service analytics tools, and

Media Query Source: Part 41 - CIO (US digital magazine); Today's most notable data strategy trend

* CIO (US digital magazine) * Today's most notable data strategy trend * Data lakehouse adoption * Combination of data lake & data warehouse The responses I provided to a media outlet on October 17, 2022: Media: What is today's most notable data strategy trend? Gfesser: Data lakehouse adoption. Media:

Community Comment: Part 23 - Architecture diagrams can often mislead

* Architecture diagrams can often mislead * Databricks isn't a storage solution * Databricks is a Hadoop successor * Both ETL and ELT involve input & ouput The comments I provided in reaction to a community discussion thread. Product Manager at Data Modeling Product Firm: It's interesting how data storage

Community Comment: Part 22 - The phrase "it depends" is still relevant!

* The phrase "it depends" still relevant * Decisional factors need to be accounted * Never bow to unjustified pressure * Your clients & customers will thank you The comments I provided in reaction to a community discussion thread. CEO at Consulting Firm: Software meetings best practices: ❌ Never say: Never. ✅ Always say: