white paper cubicsystemachitecture

8/4/2019 White Paper CubicSystemAchitecture

1/3

CeTris GmbH Grtliweg 15 CH-6300 Zug Schweiz Tel. 041-511 75 10 oder 079-307 33 05 [email protected] www.cetris.ch

CeTris GmbHCommunication

Cubic System Architecture

Manfred JehleCEO / General ManagerCeTris GmbH

I'm not very happy with most of the system and software architects.

The angle of vision of most of them is limited to their own experiences. We do

not generate systems for only a couple of years! Many 'evangelists' dispute in

circles and always around the same arguments. "We need a hierarchical archi-

tecture" or "We need a scalable and flexible architecture" or both but what will

we need in the future? What kind of flexibility will be needed within the next

10 or 20 years?

Hierarchical systemsHierarchical systems split the response into mana-geable parts. Each has its own speciality and the

work is predefined. The traffic is limited to the

system and speed is limited by the slowest tier.

The security aspects are manageable and also the

backup. In case of system failures it's possible to

get an interruption for a longer time.

The total system is scalable and most parts can

also be split to different systems.

Communication between the layers has a big im-

pact on the speed of the total request time!

Most of the response time will be lost on data con-

versations between the layers!

Scalable systemsOne of the biggest handicaps of hie-

rarchical systems is the inflexibility

of response time. Some tiers can't be

split to different server or services

without involving a huge code for

scaling layers.

The strategic goal for the scalable

system is to build primarily a system

which is scalable. The hierarchical

aspects are less important. Targets

are to share memory or system

spaces or process time. And how to

implement functions that are avai-

lable in services on different systems

and how to get the fastest responsetime for different requests.


2/3



GenGeration of systemsThe most system architects are

not interested in past systemgenerations.

Mostly they don't have to be in-

terested in the future of the sys-

tem at the time the next gen-

eration of the system should be

ready they have another job or

work for other projects or com-

panies! In the lifetime of a sys-

tem the basic architecture is one

of the most important steps for building growing systems. The lifecycles of sys-

tem parts are different. A database has the longest one up to 30 years. Base

functionalities of stable development languages get up to 15 or 20 years. Oper-

ating systems lifetime go down to 10 years depending on the hardware. In this

time line many functionalities and services come and go!

The effort to rebuild such a system is immense! To append new services and new

functionalities during this time needs a superb knowledge of the existing system.

Cubic system architecture 1)I created this perception with re-

gards to the comprehensive aspects

of all basic system architecture

strategies. The global view of a sys-

tem generates other viewpoints for

coming requirements and let us

builds scalable, n-tier and future

orientated systems.

One of the necessary skills is the ex-

perience of system and software ar-

chitecture. Another one is to avoidevangelism on architecture. The view must be one of an integration of hierarchi-

cal, scalable systems with good deals for the future.

Don't be afraid of the discussion and the fundamentalism in program languages.

Time will show you the right way to go a programming language is only a tool

to fulfil your system vision the same is essential for services think in visions

and build your hierarchical, scalable system. Use known and approved tools and

beware of unknown and unapproved system tools and parts.

Keep all as simple as possible and create everything as stable as possible! You

will need a lot of time to find all possibilities of failure in your system!

Keep in mind you need your sleep for upcoming systems leave your night-

mares behind a well-elaborated system.

1) Perception generated by Manfred Jehle, copyright by Manfred Jehle since 2007


3/3



Manfred Jehle, Zug

No extract or the whole text is allowed to use without permission of Manfred

Jehle. The Perception "Cubic System Architecture" is permitted by Manfred Jehle.

white paper cubicsystemachitecture

Documents