Concepts like micro services and antifragility are currently trending in our community and this might be a hint that there are some new architecture paradigms on the horizon. Even if not, those terms describe ideas on how to not only make teams agile but also the software itself. So what are micro services and how might they help us to design and implement software systems? Well, we are using means of decomposition throughout our systems - methods, classes, packages and modules. And in the end, we put all that in a big monolith and hand it over to production … Micro services take the concept of decomposition right to our runtime environments and let us design really loose coupled systems. Those systems are built to handle the failure of single components, they are easier to test and to maintain. Last but not least, they support the idea of continuos delivery, which is also more about dealing with a lot of small changes than huge releases. The flexibility resulting here enables us to pursue one of the central paradigms of agile development not only on an organizational but also on a technical level: Embrace change!

2. Things that gain
from disorder

3. What doesn’t kill me
makes me stronger

4. Fragile systems cannot adopt to
shocks - unpredictable, volatile and
random events.

5. Love your stressors,
gain from them!

6. „I am putting myself to the
fullest possible use,
which is all I think that any
conscious entity can
ever hope to do.“

7. Antifragility needs
the will to live

8. Be prepared.
Pull the plug.
Anytime.

9. design for each component to fail,
like a cell within an organism

10. Don’t fear perfection
you will never reach it

11. The need for change
is yet another stressor
(sdtimes.com)

12. We know how to
work with agile
teams and
processes

13. But do we create agile
software?

14. Avoid collateral damage
by truly splitting up systems

15. enter stage
Microservices

16. SOA for Hipsters

17. so what is the size of a
microservice?

18. Any piece of software reflects
the organizational
structure that produced it.
Any organization that designs a
system will produce a design
whose structure is a copy of the
organization’s
communication
structure
(thoughtworks.com)

19. everybody is an
island

20. everybody is an
island

21. Fight the
fail whale

22. Defend your
app

23. There’s no such
thing as free lunch

24. Don’t treat them like pets,
it’s cattle

25. Thanks!