Given the breadth of knowledge required to be able to deploy on the Asyncy platform, understanding how all the components work together might seem challenging. This article attempts to explain these moving parts briefly.

There are three main aspects to this:

  1. The Asyncy Hub, consisting of OMG compliant services
  2. Storyscript
  3. Asyncy Runtime
The Asyncy Ecosystem

The Asyncy Runtime/Platform

This the cloud platform on which apps written in Storyscript are deployed to. The Asyncy runtime pulls down containers from Docker Hub (or any other container registry), configures them as Kubernetes Pods and Services, then manages the data moving between the containers through the help of Storyscript.

Storyscript

A simple and human readable DSL which describes how data flows across your containers.

United we stand, divided we fall.

Storyscript glues microservices together. It tells a story of how microservices and functions interact with each other, providing a super high level programming language. We like to call this Service Oriented Programming.

It's fairly straightforward, with the core of it's structure focused around the following:

<service> <action> <arguments>

If you look at the structure of the OMG, you'll find a very close resemblance to the above pattern. Services have actions, and actions have arguments. This is the principle of the OMG.

The Asyncy Hub

The Asyncy Hub consists of services which are OMG compliant - these are the usual Docker containers created with a microservice.yaml file in them. This additional file describes:

  1. The startup and shutdown lifecycle of the container
  2. The actions and how to invoke them via HTTP (or other ways)
  3. Configuration required (such as as environment parameters) to be made available to the service

These OMG compliant services need to reside somewhere, and right now, that's the Asyncy Hub. It's the same as the Docker Hub, except that it contains automatically generated documentation around the services (since the microservice.yaml is self documenting).

The Asyncy Hub is a central repository for services contributed by other open source developers (even companies) just like you. You're free to use any service from the Hub. If you can't find one that suits your purpose, you can build one and make it publicly available!

And that's it!

Interested in deploying your first app on the Asyncy Platform? Check out the getting started guide.