Reactive Stories

APIs are often much less interesting than the stories they tell... or the stories you can create with them, i.e. systems, apps etc. The behaviour of these systems as a hole... that's where the value of the system is.

$mock say.hi (name ?= "Harry") => (greetings = "Hello, " + name)

Having an API is easy - here's one just above (one that you can edit and fiddle with). How do we specify our expectations about this value? How do we communicate it, record it, share it, cooperate on it?

In the modern age, enterprises are transformed by microservices, APIs and reactive principles.

If you want to take a refreshing look at microservices requirements, acceptance and truly continuous testing, while fiddling with the architecture itself, become part of our limited preview .

Your email

Your invitation

Need an invitation?

Your email


Stories | reactive

Evolve requirements.

Collaboration | markdown

Starting with markdown-based collaboration.

Blog | scala

Scala, functional, reactive, DSL and other topics.

Notes | journal

Online creative notes app.

If you are interested in any of these technologies and ideas or have any question on these or other topics, drop us a note with your contact info and everything and we'll gladly discuss it.

Was this useful?    

By: Razie | 2017-06-15 .. 2020-01-11 | Tags: admin

Viewed 156 times ( | Print ) this page.

© Copyright DieselApps, 2012-2021, all rights reserved.