Reactor

We reached the next staged to make Reactor to be more simple to demonstrate. Till now, it was possible to try it out through Swagger-ui and a chatbot, but from now on you can play with a browser based responsive UI to learn about Reactor. This UI enables all operations about cart based service manipulation: open a cart, order or remove product offerings or drop/commit a cart as you wish.

Waking up at the morning and checking how Reactor demo environment is, I recognised the setup of Santa Claus present and birch. Not only do Santa exists but he follows novelties!

In the last article you read about our project experiences using OpenAPI. Here you can learn about the target we had and the product we implemented. On the top of the information, you gain a demo access to the solution too what we call Reactor.

Reactor was made to serve each type of front-end applications, who want to handle multistep service manipulation carts. The interfaces have sophisticated data structure to minimise the API requests, like an add operation can respond with the new CurrentPortfolio state of Reactor transaction together with the update AvailableProductOfferings list. Other it is fine for many applications, others require simplified interfaces having predefined standard response structures. One example is chatbot.

We may say that OpenAPI is the latest craze on the field microservices. Otherwise it is also true that this specification helps a lot to implement standardised APIs. We gave it a try to implement our new portfolio element interfaces on OpenAPI basis and this article is to share to you our hands-on experiences. The results of the development, where we collected the expereinces below, will come soon.