Video není dostupné.
Omlouváme se.

Building Evolutionary Architectures • Patrick Kua • GOTO 2017

Sdílet
Vložit
  • čas přidán 14. 08. 2024
  • This presentation was recorded at GOTO Berlin 2017
    gotober.com
    Patrick Kua - CTO at N26
    ABSTRACT
    In our industry, one of the only guarantees is change. Many of today’s tools, technologies, and business models will soon cease to exist, only to be replaced by newer ones. Architects face the challenge of planning for today’s systems knowing that the problems of tomorrow will be completely different from the problems of today. Evolutionary architecture is an architectural approach that prioritises change [...]
    Download slides and read the full abstract here:
    gotober.com/20...
    / gotober
    / gotoconference
    gotocon.com

Komentáře • 8

  • @jaraxel888
    @jaraxel888 Před 6 lety +4

    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?

  • @zebmason6530
    @zebmason6530 Před 6 lety +3

    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.

  • @MachielGroeneveld
    @MachielGroeneveld Před 6 lety +8

    Evolution doesn’t happen randomly. The mutations are random.

  •  Před 5 lety +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’

  • @RiczWest
    @RiczWest Před 6 lety +1

    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.

  • @delamberty
    @delamberty Před 5 lety

    What software are you using for your deck?Great talk and well made deck

  • @sahilrealme7512
    @sahilrealme7512 Před 5 lety

    Nice talk

  • @papanino4415
    @papanino4415 Před 5 lety

    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.