Large web-scale systems have many sub-components that interact and depend on each other. The relations between these sub-systems are not evident from just looking at them.
For example, in an event driven system a publisher of an event might not know all subscribers. The different relations become even more clouded when we want to take the ephemeral nature of runtimes into account. Web-scale systems often scale up or down based on some metric, this means that a new dependent sub-system could be added or removed at any time. Is there a way to map the relations between sub-systems of a web-scale architecture that also take scaling up and down into account?
Info Support is specialist in maatwerksoftware, data solutions, beheer en trainingen en is vooral actief in de sectoren agrifood, energie, fintech, mobiliteit, pensioen en zorg.
Wij geloven in vakmanschap. Onze 500 software engineers zijn de drijvende kracht achter toekomstige innovaties. Innovaties die onze klanten vooruit helpen. Of je nu op het punt staat van afstuderen, aan het begin staat van je...