Smart Cluster approach: Open Connectivity & dezentralized intelligenz
Smart Cluster approach summary...
What is a Smart Cluster?
Smart Cluster = Open Connectivity + Connected IntelligenceBe open and free to changes in the IoT, it primary needs two parts: loose coupling and a decentral organized intelligence.
The challenge of today's approachesAre you continually confronted with uncooperative standalone solutions?
Are you eager to break open rigid structures and systems to unlock new synergies?
Would you like to reveal the potential of a smart system-wide network?
Are you looking for IT systems that are modern, integrated, secure, and ready for the future?
The multitude of different IT landscapes also poses another problem: Over time, these have often evolved into monstrously large and usualy closed systems. It’s often very tricky to adapt these to satisfy changing requirements – and it can come with great effort and risk.
The solution lies in our special approachWe are adaptive: We use manufacturer-independent open standards – to keep all our options open, for today and tomorrow.
Small, smart components (e.g. microservices) and transparent interfaces (EventBus, RESTful APIs) finally make it easier and cheaper to respond to evolving needs as required.
The strength of our approach lies in the use of a common configuration center – the infrastructure repository. This repository holds a record of all systems and components. When changes are made, all dependent components are automatically updated with the new settings.This ensures that communication across the system is secure, fault-tolerant, and completely integrated – with full transparency and control.
What you archive with a Smart Cluster
IndependentDesign all interfaces to be independent from type of platform and programming language
Uniform InterfaceUse common basic functions and pure structured data (document style). Here it will be quite useful to have a closer look to the RESTful design principle.
StatelessDon't use session, cookies, tracking parameter and other implicit kind of temporary status storages. As they block resources, hide communication workflows, make usage complex and are risky for security.
TransparencyBe open. Provide the API for everybody. Use a common infrastructure database, from which all configurations can be taken, and to which all current used interface parameters can be written.
LayeredBest of breath: For each layer, have the best fitting technology. Use established standards wherever possible. Don't reinvent the wheel.
Data CentricWherever possible use the business driven data structures. Doing so the API will be the natural base for business discussions.
ScalabilityScalability means parallel handling. Best by using small technical clusters (like Microservices). Note, that this is the opposite of monolithic systems.
Event bus / notificaton bus / message busFor the successful communication in connected systems, a publish-subscribe notification bus (like MQTT) does perfectly fit. With such, all kind of data and events can be handled as a cached in a queue for all interested nodes.