Quick thought: The longer you use old tools to glue old systems together, the less likely you'll be able to integrate or manage new problems. (There's a bit of a leap there, but not much.)
One of those variables needs to change over time for your operations to stay healthy. You stick to one toolset for a decade and you won't be able to hire anyone with less than a decade's experience in that toolset to manage it.
Which you may choose to do, for lots of reasons. But you're stuck in a decades-old toolset then. Do you have any idea what you can't do because of your current toolset?
Sunday, February 10, 2019
Subscribe to:
Posts (Atom)
The point of this blog
Welcome to the beginning of the film
In the twenty-plus years I've worked in data management I've spent a lot of time having some version of the following conversati...
Top 3 Posts
-
Nobody knows how to build an ODS, or why you might build one. I've had many many many arguments with "data warehouse developers...
-
3.6 Patterns of organization There are a couple of simple patterns you should consider when organizing your data management efforts for maxi...
-
4. The data management ecosystem There are only a few components to the modern data management ecosystem, which is displayed in the diagra...
