It also crosses over into governance topics, like how to define a customer and where the ownership of that official definition resides. It may involve technical modeling like building a dimensional model, but also involves abstracting that model into a conceptual model that business stakeholders can understand. I view it more as understanding what the data is, where it resides and how to put it all together to meet the business objectives. I actually was assigned to an engagement as a data architect in my super impressive consulting company and the engagement lead couldn't define what he wanted me to do. If you organisation runs courses on leadership or stakeholder management, influencing others - soft skills- I’d sign up.įrom my experience the definition can very and as noted before, not many people understand it. The hardest one to maintain is with engineering who often see you as an overpaid line & box drawer. Keeps senior people happy, engineers happy, product owners… basically you are semi stuck in the middle trying to keep everyone happy. Last one, most important skill seems to be stakeholder management. ![]() Present options and a recommendation, highlighting concerns, risks and assumptions, can’t go wrong really with that approach. The solution isn’t always technical either, the skills of the people around you will influence your designs. With everything there is never one answer, and be pragmatic (good architects are). Probably less stuff on the internet about this. Give you more of an understanding as to why people do different patterns.ĭifferent data migration approaches are worth having up your sleeve. You could read around the topic of service oriented architectures. Event hubs, functions… and then what the industry is using Kafka … Learning about pub/sub: publish and subscribe patterns. You could also go down the data engineering associate certification if you want to just focus on analytics. Having a quick look at the certificates (I know the AWS ones better) yes the solution architect certification route looks good. I don’t have any certificates myself, partly because I hate studying :) Why it matters when looking at solutions. ![]() learn some different patterns for data solutions. Everything has data in it, use it as an excuse. Ask to be involved in other “data” projects. Attend some conferences online and or in person C4 models, process modelling, master the art of drawing azure architecture diagrams (drawio or Visio) If you have an enterprise architect see what they do Shadow the other architects in the organisation And the odd time I’ve had to justify my role and where I add value - very odd. And since I’ve been a data architect, I have been to at least four organisations who openly admit they have no idea what a data architect does (they literally recruited me but no idea why). The data engineer route tends to lead to greater opportunities. Head of architecture seem to be more application/software architects. Once you get to enterprise architect that is normally it. Cloud skills I would say are a must nowadays as an architect, but I still meet lots who don’t know how to deploy their solutions to the cloud or even know which resources to use and why. You could actually go broader and learn some of the skills other architects have. And some companies think you just do analytics. I am happy doing all three, some companies expect you to do them all. In the modelling world, the enterprise conceptual data model, standards…. Able to work analytics, application, data migration … and roughly understanding how that fits into the enterprise.Įnterprise data architect - doesn’t know or need to know technical how things work.pre focused on what the business is trying to do and what Data capabilities are needed to deliver those. Solution data architect - broader skillset. Responsible for a specific system and the fine detail of how that system works. Technical Data Architect - bordering on senior data engineer. And then there are three levels in each of those. People either become data modellers or technical. And I think it really depends what you want to do as an architect. ![]() Not because the work is hard, because no one really knows what you do.ĭata architecture can be split many ways and the roles all differ. I’ve been a Data Architect for 10 years now and it is really a tough role to do.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |