[http://creativecommons.org/licenses/by/3.0/]
This work is licensed under a CC
Attribution 3.0 Unported License [http://creativecommons.org/licenses/by/3.0/]
@dret
on Twitter/GitHub
The idea of digital transformation leads many organizations to more decentralized IT architectures: Instead of driving IT top-down in a one-size-fits-all approach, the goal becomes to move away from mandating one single way how to build applications. The focus then is on what needs to be done to create and manage a loosely coupled and evolvable landscape of digital products. These landscapes not just evolve in terms of the products that are developed in them, but they also evolve in terms of what the landscapes support, and possibly what kind of tooling is made available as a service to product teams. Continuous Architecting is a new way of thinking about architecture, where the main goal is to observe how well the capabilities and constraints of an IT landscape work for product architects, and to continuously adjust and improve these capabilities and constraints, so that products can be designed, developed, and deployed more easily.
@dret
on Twitter/GitHub
APIs for Things)
Continuous API Management: Making the Right Decisions in an Evolving Landscape[https://www.apiacademy.co/resources/books/continuous-api-management]
proto-APIsfrom integration projects
Engineering the Engineers
landscape areas
dret.net/lectures/vss-2019
[http://dret.net/lectures/vss-2019]@dret
[http://twitter.com/dret]linkedin.com/in/netdret
[http://www.linkedin.com/in/netdret]dret.net/netdret/
[http://dret.net/netdret/]