[HN Gopher] Dismantling ELT: The Case for Graphs, Not Silos
       ___________________________________________________________________
        
       Dismantling ELT: The Case for Graphs, Not Silos
        
       Author : sebg
       Score  : 24 points
       Date   : 2024-11-28 08:02 UTC (14 hours ago)
        
 (HTM) web link (jack-vanlightly.com)
 (TXT) w3m dump (jack-vanlightly.com)
        
       | smitty1e wrote:
       | It's a great theoretical point.
       | 
       | > The tools, the practices, all built around the premise that
       | software and data teams don't work closely together.
       | 
       | In particular, the various teams, even the same team with itself,
       | end up being separated along a timeline.
       | 
       | Information Technology ends up being the embarrassment we all
       | face that our data are rarely, if ever, showing up dressed for
       | work.
        
       | jacknews wrote:
       | Since the article uses lots of big words, phrases and memes (when
       | a few simple words would suffice), and assumes you know it
       | already, Conway's law is simply that your technical architecture
       | will reflect your social/organizational architecture.
        
         | orbat wrote:
         | "Big words, phrases and memes"? You got this distressed about
         | an article using industry standard terminology for its target
         | audience and assuming that you'd read (or would read) the post
         | it linked to on Conway's law?
        
       | arkh wrote:
       | > provide "data APIs" to data teams
       | 
       | I feel like I'm reading part of Data Mesh again.
        
         | robertlagrant wrote:
         | Hah. That is a good reference. Never seen a concept boosted so
         | much.
        
       | dallasg3 wrote:
       | I hate to say it, but good documentation is the key here.
       | Visualizing data as interconnected nodes breaks down silos,
       | aligns teams and makes it easier to build reusable, loosely-
       | coupled systems.
        
       | tspann wrote:
       | reminds me nifi plus kafka
        
       | datatrashfire wrote:
       | I missed the part where there was an actionable takeaway about
       | how I as a practitioner am supposed to differently.
        
       | baq wrote:
       | Conway's law works both ways: if you want a system to be designed
       | in a certain way, you create an organization who is building it
       | in that way.
       | 
       | So, if you want a data mesh, build a mesh org. Not the easiest
       | job.
        
       | chevman wrote:
       | Been in BigCo land for 20 years now, and have seen the rise and
       | fall of quite a few data/analytics/BI/reporting/AI/ML fads.
       | 
       | Honestly the whole landscape seems broken and unproductive at
       | this point.
       | 
       | Countless vendors, platforms, cloud environments,
       | industry/technical jargon - all with different pricing models,
       | SLAs, tooling, etc etc.
       | 
       | Getting anything usable is a challenge and most orgs spin in a
       | never ending cycle of data integration/normalization work that
       | produces little business value.
       | 
       | My advice to teams now is simplify, reduce, streamline - get to
       | the kernel of what you think you need and protect it all costs.
       | Most of the shiny new objects being pitched as silver bullets are
       | just ways for other people to make money off your margin.
        
       | heisenbit wrote:
       | The article does not contain the words performance and security.
        
       | up2isomorphism wrote:
       | Yeah, 100 people can literally implement what he is saying in 100
       | different way.
        
       ___________________________________________________________________
       (page generated 2024-11-28 23:01 UTC)