[barbegal]

What about this is agile?

>We can set up the assumption that today, each new application supporting API should be a cloud-ready application. By cloud-ready, we expect that it should have the following properties: The ability to adapt dynamically to the load, A flexible and centralized configuration A dependency discovery mechanism, A native load-balancing mechanism for communicating, Strong resiliency, monitoring, and observability, Automatic log and distributed traces collection

This sounds like over-engineering (the exact behaviour that agile is designed to counter). There is too much focus on tools and processes rather than the working software.

A more agile way would to create a working API with basic tools but in a way that allows adding the extra features (logging and load balancing) at a later date.

[ams6110]

> There is too much focus on tools and processes rather than the working software

That's because this is a marketing piece for Red Hat tools and processes. All you really need to implement the API they describe is a database, a web server, and a few lines of glue in some scripting language or other.

[donttrack]

They might as well have chosen to journey to an application, that print "Hello World" on the screen, but it would probably have been too obvious a marketing piece.