This is the second blog in a series of 3 blogs about the Velocity Conference 2019 in Berlin. Read the second blog here!
Thursday: Even more keynotes, sessions and the inevitable trip back home
How to deploy infrastructure in just 13.8 billion years Ingrid Burrington (Independent)
A talk about the history of the universe and how we got to computer. It was a very abstract talk, but in the end, I think the gist is that computers are still a very young field and we should work on the future of the technology instead of maintaining the status-quo of the systems of today.
Bas LangenbergBAS @O’REILLY’S VELOCITY CONFERENCE 2019 – Last Day
This is the first blog in a series of 3 blogs about the Velocity Conference 2019 in Berlin.
Within SynTouch, I try to be on top of the next big thing from infrastructure perspective. Therefore, I went to O’Reilly’s Velocity conference, in my opinion one of the best conferences someone in my area of expertise can go to. This blog is my report on my experience. I wrote down what I took away from the conference and most important, my lessons learned. This blog is a mixture of my own opinions and those of the speakers.
Bas LangenbergBas @O’Reilly’s Velocity Conference 2019 – Berlin
A city trip to Enterprise Architecture – an analogy
Enterprise Architecture may be hard to grasp. Especially for people who have little feeling with this topic. An analogy usually helps explaining it. One that works pretty fine to me, is a city. This city-analogy allows me to project map enterprise architecture on common life concepts. Both enterprise and city are comparable as they have goals, an organization structure, functions and processes. Buildings in the city resemble applications; roads the infrastructure; people and goods the data.This article dives a bit deeper into this comparison. It discusses and compares architectural aspects and roles (see also my blog on architecture roles)
Harald van der WeelCity trip to Enterprise Architecture
“What architects do I require in my organization?”, “What architect could I be?”. Two different questions. One from a customer, the other from a colleague or job applicant. Both questions are related: They both assume (in a way) a clear distinct separation of the architecture domain into roles. Based on job titles, advertisements and function-descriptions there are dozens of architecture-roles used in the field: information architects, enterprise architects, solution architects, software architects… and so on, and so on. You most likely have a feeling about their supposed meaning and responsibilities, just like I do.
Harald van der WeelStructuring (a forest of) architecture-roles