Introduction of 2S platform 40% done

DANGER

The platform is under development. See the road map.

The 2S platform, as I call it, should help you to manage your products and complex monolith application(s). The 2S represents Simplicity and Subscription-based platform.

INFO

I will use many expressions in the text that are described in the section about the modulith architecture, for example, ecosystem and satellite. If you don't know them, I recommend reading that section first.

The platform is used to describe the relationships and the building blocks in your ecosystem, plus it should help you manage it by intelligent monitoring, centralized configuration, and real-time event-based system logs. Everything is done by three independent actors, which can be used in combination or separately:

• Storyteller
• Supervisor
• Scheduler & Initiator

The storyteller describes the entire business structure and dependencies in the ecosystem, and it acts as documentation and the subscription service for the runtime. The second part, the supervisor, is a clever and real-time system watcher. The last and most specific actor is a flexible scheduler & initiator of jobs or work units if a lot of time-based or event-based processing is needed and monitoring of them in a sustainable way is required.

TIP

The platform is designed in a way that should help you understand the modeled ecosystem and act as documentation. That is extremely handy when you bring new faces to your team. Another superior concept is to speed up reverse engineering and debugging in case of an incident. As I mentioned many times transparency and visibility are some of the most fundamental properties of a healthy product.

The actors are open-source, allowing you to deploy them on-premise, under your cloud account, or into any hybrid environment. If you need to bend some parts, please be your guest and create a PR with code changes. The other option is to subscribe and consume it as Software as Service (SaS). In this setup, you don't need to take care of anything, and you will get some extra polish tooling plus reporting.

The deeper dive into the concepts is done in the next section of overview, or if you would rather see it in action, please jump directly to live demo page, where is a reference example of the modulith and you can see the platform in motion.

The annotation guide

Storyteller is the actor that holds the catalog. The pages below explain how a product is described with annotations, how configuration stays flexible without a private copy of every deployment, and how that looks on products that are already in production somewhere.

• Annotations — the seven records, what each one is for, and how they are addressed
• Configuration — store the difference once, read the merged setup
• How to model a product — which noun becomes a subject, a context, or a responsibility
• Using the platform — the scopes, the reads a service makes, and the writes that build the catalog
• Examples — a B2B SaaS, a consumer finance suite, a distributed platform, a versioned monolith, a physical product, and a device fleet