Architecture Overview

Phoesion Glow is based on a distributed micro-service cloud architecture.
The separation of flow to components Mediator<->Bus<->Services allows you to create a highly-available, fault-tolerant and secure cloud solution in any way or configuration best suits your needs.
Architecture

Cloud Entities

Phoesion Glow Prism

Prism is the only element exposed to the world and acts as the mediator/gateway between the world and your services.
It can receive requests from HTTP, WebSocket/SignalR, MQTT or other protocols, and will forward them to the appropriate back-end service (Firefly) using the service bus (Kaleidoscope).

Phoesion Glow Kaleidoscope

This is the service bus for the entire cloud, used by all entities to communicate with each other.
Kaleidoscope is responsible for authenticating and message routing/queueing to/from all entities. (eg. Prism<->Firefly)

Phoesion Glow Firefly

This is the element responsible for running your actual micro-services.
Fireflies are responsible for retrieving, hosting, running and managing you final service code.

Phoesion Glow Lighthouse

Lighthouse is the command-and-control center.
Developers can connect to the lighthouse and from there monitor and manage the entire cloud (eg. deploy your code). The Lighthouse distributes your service files and configurations to the Prisms and Fireflies

Developers

Phoesion Glow Blaze is a set of tools and utilities developers can use to manage the entire cloud. From Phoesion Glow Blaze a developer/admin can connect to the lighthouse and create new Quantum Spaces, deploy micro-services and monitor the cloud health.