Complex systems architecture

When one person can no longer describe the system.

Some operations restart their environment several times a day, and no one can detail the parts, the functions, and what the whole makes emerge. MC3D has designed that architecture since 2006. The layer is written down, and the operation does not shut down to redraw it.

Write to MC3D See the layers

01 · The signal

It does not close

Parts, components, functions, and the emergent property no longer fit in one person's definition.

02 · The layer

It is written down

What stays in the core, what is integrated, what a rule decides, and what stays visible.

03 · The scope

600 applications

On a single project, the architecture reached that number. The core stayed in production.

Two approaches

Not every operation asks for the same layer

Systems architecture orders what can already be described. Complex systems architecture comes in when that description no longer fits in one person.

System

It serves to optimize what already runs, gain efficiency, and adapt without a complexity that no one can govern.

Complex system

It serves when the environment moves, the failure cannot be isolated in one component, and uncertainty is part of the operation.

Reference

The model follows the operation

It does not start from an empty framework. It uses the one the industry and the system already recognize.

MDA

Design and development stay aligned. The trace between them can be walked.

SOA 2.0

Acceleration, transformation, and rules blocks, across more than one brand. REST, SOAP, and binary services, including CORBA and the data grid.

DDD

The design walks the domain layers, not only the box diagram.

TM Forum

Business, data, application, and technology, with integration governance. It is the telecommunications framework.

TOGAF

The complete model, and the extensions the industry asks for.

Zachman

The multidimensional view of the components. It is used when the client's license allows it.

Construction

What stays running

Microservices

Change is deployed in parts. A failure does not force the application to be rebuilt.

Cloud

AWS, Azure, Oracle Cloud, and Google Cloud. Hybrid or multicloud, according to where the data has to live.

SOA

Decoupled services so the systems talk without staying stuck together.

Distributed systems

Several components, fault tolerance, and support when demand rises.

Data

Capture, processing, and reading of large volumes, also when the answer has to be immediate.

In operation

Layers already running

Santo Tomás

UST, CFT, and IPST. Oracle CRM, benefits management, Banner ERP, MINEDUC, and DEMRE on the same layer. The quotation application covers undergraduate, graduate, and open and closed courses.

Entel

Reference architecture on SOA Suite 12c and BPM Suite, a center of excellence, and the TM Forum framework, with a scope of 600 systems. Oracle ERP Cloud integrated with SAP OnPremise through Oracle Integration Cloud.

Banco de Chile

Electronic transfer landed on OSB and SOA Suite, with a rules engine: 3,000,000 combinations in 11 ms. Three clusters of 15 nodes, in two data centers, and SOAP over Tuxedo to the legacy stack. Cloud Control supervises the layer. Teletón is the same engagement.

Dirección de Presupuestos

SIGFE Agregación: a service bus, transmission agents, and a rules engine. The letter records 60% of the country's budget execution. Information generation went from three months to hours.

If the system no longer fits in one person, let's talk.

contacto@mc3d.cl