Cloudoffice Reactive Cloud©

When your frontend is full of reactive/observable components but backend communicates same old request-response per thread model than it’s like a beautiful flower bloomed at dawn but in front of dumb, blind and smell ability less community.

What is real world to human? Anything in nature is observable. You are deciding what you observe/subscribe what not.

So being observable is default, so every component’s abstract trait must be observable (surely with authorization) in a Reactive echo system and what you subscribe, should be declarative.

What it means? Its means you must not wait for others response/reaction after doing any action for that, it will get back to you with reaction when it is done and also update later on. ( e.g. subscribing something and getting notifications )

This is what in languages (programming) writers are calling Promise, Future.

What is the benefit? You are not blocked! But what if you need it now!! It not requires to change the echo system but may be just informing back to you, can it react now or not.

What are the issues to achieve in this echo system? Are we not already in this situation? Yes our frontend more or less every component can be observable now a days but majority backend is not reactive. A few applications like Chat/Messaging applications are having Reactive backend. And rest are using request model (Sync or Async calling).

Easy way to understand the reactive feature is that your component can push information to its subscriber component. So a request model is not reactive as other component can only give you data when you request, so in mean time any changes in other component you are not informed.

So enabling push trait for all frontend and backend components of your infrastructure is what means a Reactive Cloud©.

Cloudoffice Reactive Cloud© has three core parts:

1. Cloudoffice Cockpit Framework: Where you can write Reactive HTML5 Cockpit components and its controller in Java (no need of java plugins in browser) and provide Offline data management too. For being controller in browser making use of HTML5 Storage API use is really easy.

2. Cloudoffice Reactive Network: It’s a Reactive Gateway and your network Microservice binding that enables a non-blocking reactive/push communication/websocket connection management in between Cockpit component and Cloudoffice Reactive Microservice component. Here you can also bind/attach clients of non-reactive third party servers e.g. oauth, network health.

3. Cloudoffice Reactive Microservice Framework: API to write non-blocking i/o based Mircoservice Component that can be registered in Cloudoffice Reactive Network.

If you are a developer, we are planning to come up soon (hopefully mid next year) with SDK and archtype with IDE support where by creating an online account you can develop using our API, frontends and micro services not only with java but also with JVM supported functional languages.

If you are a system admin, we have plan for console program to manage and to do your favorite scripting to run batch operations ;) invoking and piping microservices in the network.

If you are a technical project manager and feel interested. We are open to discuss and have technical sessions, so that you can evaluate our architecture and so far developed POCs to create your next dinosaur.

If you are hosting/cloud provider, may be it is for you ;). We are open to discuss.

If you are Agile master, may be you can think of Reactive Agile© where developers can act as developers not employees; without any pressure.

If you are tech investor and feel interested, please only approach if you understand I/O business and have proper time for that. We are looking for skills together with fund.

Please feel free to write to me for any query:

BTW, this is nothing unique idea development but rather whole industry thinkers and giants and languages are trying to adapt this too as this is what future is.

Manna, Cloudoffice