Research Docker stacks for summarization of containers #635

New issue

Closed

opened 2026-04-29 07:01:05 +00:00 by a24timsv · 3 comments

a24timsv commented

2026-04-29 07:01:05 +00:00

Collaborator

Read about docker compose and docker stacks.

Some stacks might be able to function separately from everything else, but some containers need a common container to communicate (how all sensors communicate with the middleware through MQTT). Each stack CANNOT create its own middleware or MQTT, but needs to use the same.

For sensors, the generate, reader, Postgres and service, could all be a part of the same stack.

Post findings here.

Currently all containers are started in a single compose/stack. This unnecessarily complicates building and maintaining containers. Research how we can create smaller components of containers to make developing easier. Read about docker compose and docker stacks. Some stacks might be able to function separately from everything else, but some containers need a common container to communicate (how all sensors communicate with the middleware through MQTT). Each stack CANNOT create its own middleware or MQTT, but needs to use the same. For sensors, the generate, reader, Postgres and service, could all be a part of the same stack. Post findings here.

a24timsv added the

enhancement

help wanted

project documentation

backEnd

research

labels

2026-04-29 07:01:05 +00:00

hGustavs commented

2026-04-29 12:13:09 +00:00

Owner

This is a central problem for all micro-service architectures... hopefully there is a suggestion/framework for resolving this. There may even be research papers on this topic.

c24carso was assigned by a22erigr

2026-05-06 07:17:05 +00:00

a22erigr removed the

help wanted

label

2026-05-06 07:17:09 +00:00

c24carso commented

2026-05-06 16:10:23 +00:00

Collaborator

Research

Paper: https://arxiv.org/abs/2305.11293 analyzed 200+ open-source projects and identified common patterns for how containers are grouped in compose files. The paper touches on the problems mentioned in this issue, more specifically how services interact through shared networks, how compose files can be split across a repository, and how shared services like middleware can be accessed by multiple stacks.

Docker Compose vs Docker Stacks

Docker Compose and Docker Stacks both use the same compose file format but are meant for different things. Docker Compose is for local development on a single machine. Docker Stacks is part of Docker Swarm and is meant for production deployments across multiple machines. For our project Docker Compose is the better fit.

How to split with Docker Compose

Docker Compose supports splitting services across multiple files using external networks. One file creates a shared network, others join it with external: true. Services across files can communicate by service name as long as they share the same network. This is how shared services like middleware and MQTT can stay accessible to all stacks without each stack creating its own.

No new dependencies or tools needed.

### Research Paper: https://arxiv.org/abs/2305.11293 analyzed 200+ open-source projects and identified common patterns for how containers are grouped in compose files. The paper touches on the problems mentioned in this issue, more specifically how services interact through shared networks, how compose files can be split across a repository, and how shared services like middleware can be accessed by multiple stacks. **Docker Compose vs Docker Stacks** Docker Compose and Docker Stacks both use the same compose file format but are meant for different things. Docker Compose is for local development on a single machine. Docker Stacks is part of Docker Swarm and is meant for production deployments across multiple machines. For our project Docker Compose is the better fit. **How to split with Docker Compose** Docker Compose supports splitting services across multiple files using external networks. One file creates a shared network, others join it with external: true. Services across files can communicate by service name as long as they share the same network. This is how shared services like middleware and MQTT can stay accessible to all stacks without each stack creating its own. No new dependencies or tools needed.

c24carso added the

needs review

label

2026-05-07 10:21:21 +00:00

a24timsv referenced this issue

2026-05-08 17:31:25 +00:00

Check status on the separated databases #825