I might have been living under a rock, but system level architectures have always been paramount to all the projects I worked on. From the start of the project / system in perpentuality. By definition of an evolving system the architecture changes and in small teams it's the team or tech lead, in large orgs it might merit some overall architect. Has the software world lost its basic knowledge over the last decade that these concepts need to be justified?
5 ปีที่แล้ว +2
when i read ‘evolutionary architecture’ i was expecting an approach which would allow me to evolve from unikernel to monolith to event-driven to microservice, but instead got a (useful) guide on how easy is to grow each one, and how to ensure properties are maintained. so perhaps a more appropriate title would be ‘growable architecture’
He glossed over coupling and cohesion. I didn't think I really learnt what Evolutionary Architecture was about apart from the surrounding processes. Can't find a listing of the contents of the book either so wouldn't know if was worth the money.
You've got to sort of build an evolutionary sort of architecture to make sure your sort of product satisfies its sort of needs that you've agreed to with your sort of clients and sort of vendors... sort of.
![ตีสิบเดย์ [FULL] | เปิดใจ "อาจารย์ เบียร์ ฅนตื่นธรรม" นักสนทนาธรรมสายดุดัน!](http://i.ytimg.com/vi/vqaBI_mnoDk/mqdefault.jpg)
I might have been living under a rock, but system level architectures have always been paramount to all the projects I worked on. From the start of the project / system in perpentuality. By definition of an evolving system the architecture changes and in small teams it's the team or tech lead, in large orgs it might merit some overall architect. Has the software world lost its basic knowledge over the last decade that these concepts need to be justified?
when i read ‘evolutionary architecture’ i was expecting an approach which would allow me to evolve from unikernel to monolith to event-driven to microservice, but instead got a (useful) guide on how easy is to grow each one, and how to ensure properties are maintained. so perhaps a more appropriate title would be ‘growable architecture’
He glossed over coupling and cohesion. I didn't think I really learnt what Evolutionary Architecture was about apart from the surrounding processes. Can't find a listing of the contents of the book either so wouldn't know if was worth the money.
Evolution doesn’t happen randomly. The mutations are random.
What software are you using for your deck?Great talk and well made deck
There’s some good points, but it doesn’t hang together and has too many “thought-works-thoughts” mixed in so it’s really quite confusing.
Nice talk
You've got to sort of build an evolutionary sort of architecture to make sure your sort of product satisfies its sort of needs that you've agreed to with your sort of clients and sort of vendors... sort of.