Sneak Peek to Service Operating System…

Formalizing the model for “Apps” in the information and service ecosystem has kept the team quite busy. In the recent discussions about “How is The Ball platform related to the services?” we came to quite a good explanation of the whole concept.

The Ball can be thought of Service Operating System. It is target platform agnostic, so it deploys on any technology stack with ease (thanks to ADM). It runs everywhere natively… so it’s logical platform rather than a platform. The design models however do require certain primitives:

  • Data Storage/Retrieve (storage space & storage transactions)
  • Data Processing (CPU time & runtime memory)
  • Processing Queues (storage space & storage transactions)
  • Transmit (transmitting the data, network bandwidth)

While the blog has been silent for way too long and we’re still polishing the whole concept I wanted to share few images, that might make sense to those already familiar with “The Ball” (for those NOT familiar, but interested, “The Ball” is described in previous handful of posts starting from August 2012).

Service Operating System (SOS)

“Apps” running in security context sandboxes. Cross integration and trust management between the providers, all within control of the user.

Service Operating System Integration Overview

Service Operating System Integration Overview

This image is first one in the series describing the SOS overall and comparing it to traditional “siloed” digital service environment. In this model the integrations are controlled and driven by the user, service and “App” providers are to provide the model-compatible services and converters to enable plugging.

Master Information Management

Another topic that we’re going to better cover is information flows within the processes and implicit master information management that is supported by the core SOS engine.

Information rendering with Master Information Management

Information rendering with Master Information Management

The master information flows are supported within security contexts and between separate contexts with active “push” type subscriptions and “pull” type monitoring.

I’ll cover both the areas with better concrete examples on the running platform soon(ish). The master information management is already in full-action on the current building of “Open Innovation/Collaboration Platform” and we’ll properly aim to demonstrate it with resource level monitoring and cost-based billing on “Apps” running on the platform.

Happy beginning of 2013,

Kalle & the rest of “The Ball” team!

This entry was posted in Computers and Internet. Bookmark the permalink.

3 Responses to Sneak Peek to Service Operating System…

  1. Alex Norta says:

    That goes into a nice direction. However, to solidly “formalize”, I would rather suggest to use CPN Tools (http://cpntools.org/) while interface definitions of CPN-modules could be performed using your approach of git-instances that reference each other while these instances comprise XML-based method&data-specifications. For the latter you have then those nice open-source tools for rapit code-translation.

  2. kalleabs says:

    Thanks for bringing that service-connectability approach up! The discovery services and their logic are definitely important “user-space” services, such as catalogue and trust management services.

    Depending on all the way to individual preferences, each user and group can have their own unique combination of service providers and “The Ball” instances running SOS.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s