Swarmlab docs

Application development in a distributed system

Development of Distributed Systems from Design to Application


You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

111 lines
1.9 KiB

3 years ago
= project structure and technologies used
3 years ago
3 years ago
== Dynamic Structure
3 years ago
[.float-group]
--
[.right]
image::ROOT:swarm-poc.png[float=right]
:hardbreaks:
{empty} +
{empty}
:!hardbreaks:
.From -> To
* [*] monolithic -> networking architecture
* [*] static -> Dynamic
* [*] host based -> Service based
* [*] linear -> agile
--
TIP: You will learn to code, coordinate and orchestrate a swarm of self-acting nodes.
3 years ago
== Dynamic Instaces
3 years ago
3 years ago
[.float-group]
--
[.right]
3 years ago
image::ROOT:docker-images.png[210,260,float=right]
3 years ago
:hardbreaks:
3 years ago
3 years ago
{empty} +
{empty}
:!hardbreaks:
3 years ago
Server instances are *platform agnostic container-based applications.*
To build a large - scale distributed application we take advantage of standardized code deployments using Docker containers.
3 years ago
3 years ago
Docker-based applications can be seamlessly moved from local development machines to production deployments
3 years ago
{empty} +
3 years ago
--
3 years ago
3 years ago
== Dynamic networks - Swarm
3 years ago
3 years ago
[.float-group]
--
3 years ago
[.left]
image::ROOT:gynamic-swarm.png[320,540,float=right]
3 years ago
3 years ago
{empty} +
3 years ago
*From Code to full-blown systems*
* from a single container on your local machine
* to a running cloud native - container-based environment
* in the simplest and most logical format as possible.
3 years ago
:hardbreaks:
3 years ago
3 years ago
{empty} +
3 years ago
{empty}
{empty}
3 years ago
{empty}
{empty}
{empty}
{empty}
3 years ago
{empty}
3 years ago
Services in a dynamic and Scalable Distributed Architecture
3 years ago
{empty}
3 years ago
--
3 years ago
3 years ago
* (1) Opens the info menu
* (2) Run a shell in a running container
* (3) Opens web interface
* (4),(5) Source directory - Directory Maps
image::ROOT:types-of-mounts-bind.png[,250,float=right]
*"Directory Maps"* are the preferred mechanism for persisting data generated by and used by Docker containers. We use here "bind mounts" and they are dependent on the directory structure and OS of the host machine.
WARNING: Your local changes to the files will be overwritten by click on "Download" button. You should always *take a full backup* first (simple copy the directory tree)