OpenAPI implementation and a demo

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.

We at Telcotrend decided to implement a new software portfolio (the red boxes), which allows companies having large, slow motion elephants (the good old legacy systems I mean) and sophisticated product or service portfolio, to have a great online presence. The key item is the order capture solution in the middle (Reactor), which contains all business logics about selling and care. This second, the care is crucial because cart solutions on the market (assuming they have enough capability to handle sellability itself) has no guess about care solutions. Care is the case of continuous services, when the currently active portfolio element of a customer implies the actions they reach: which new offer they can buy or what they can change on the current portfolio elements.

I have a freaky example for you. Imagine that you are going to the mall and pushing your shopping trolley. As you picked this cart it was filled by all the goods you have at home already; e.g. you still have milk and bread. As you step into the shopping area, you will not see the milky row, it is hidden. You are looking around and you will not see any shoes, because you haven't bought socks now or before. You pick some bread and you will get the offer to buy butter, what you did not find before... The strangest case if you decide to take back the milk, means the milk you have at home just to pick out of the trolley, therefore the milky row will be unhidden... It's so crazy isn't it?

If we replace bread and butter with the examples of Gold Mastercard, which you can get only if your account is "VIP" or you will get the brand new mobile handset for free if you upgrade to tariff XXL or the case of cancelling your TV subscription - it is becoming something real and familiar. The reason of sharing the example above is only to highlight the specialities behind the continuous services, which have to run in Reactor.

Turn a bit to the multistep approach. Using this cart you can do any number of changes to see how much you would pay if you change tariff, buy handset, get some special extra services (like a data package) but before the check-out, nothing is changed on the actual state. Like a transaction in a database - before commit, the changes are only has effect inside.

To read more about Reactor product itself, please visit Reactor introduction page at the company website.

I am sure you are now ready to try the demo! You can access the demo environment at

You have three ways to go accessing the demo page:

  1. Simply to visit and overview how an OpenAPI self-defined page looks like
  2. Give a try to the environment a play a bit on the page. We made you a step-by-step manual to learn the basics. Read it before!
  3. Try to integrate the APIs into your environment.

It is your decision. Demo is free to use but it has some limitations:

  • only some rule types are working
  • no sophisiticated customer hierarchy is allowed
  • queries for cart checkout summary are not present
  • the number of operations are limited both on API keys and transactions (100 each)
  • the demo environment a single server, multitenant one, you will share the hardware resources with others - still your data is protected by the API key mechanism!

In the coming days we will share to you UI integration cases with chatbot and simple web UI, some details how Reactor may be planted into a microservices architecture and the cloud platforms we use.

Please share you mind about the demo either here in the forum, our write a mail to Reactor team!

Log in to comment
© 2017 Architect Archers