In the perspective to give a basement to ISA, here is an exploration of pros and cons of major paradigms (No paradigm, Object Oriented, Sets (Relational) and Functional). To sum up the OO paradigm is retained for ISA. It is this approach that has made me discover the “Atom Oriented” possible paradigm.
Continue reading Available paradigms overviewLuc Laf
Have an underlying paradigm to help building ISA is a mean to promote coherence and consistency.
In this way it is easier to follow all the previously expressed wishes. It also gives guidelines for choosing among solutions in particular on reuse of an existing one.
We are facing a problem where it seems we should choose between the idealism pest and the cholera of pragmatism.
Like Charles Sanders Peirce I prefer the pragmaticism word to distinguish this scientific approach of the usual pragmatism to just deal as we can with the real…
Doing nothing is always the best option when acceptable. So optionally if an existing technology is a good candidate to be an ISA part and that it meets all the requirements above, then it should be retained.
This post is also the opportunity to initiate the building process of ISA.
ISA should offer a basic common management for specification, design, test, delivery and the like.
The purpose of ISA is to provide a common set of blocks on which any people involved in software can rely at anytime and anywhere.
Another aspect ISA should address is the continuity in the problem/solution chain thru specification/realisation and the abstraction levels.
Think and design ISA to be durable for several decades. The main design patterns should be incorporated as much as possible. This architecture should not limit itself in changes that it can elaborate to have good performances. And this in both dimensions hardware and software. Remain native : It is the condition to do at best of the possible. Define a solid base and then incorporate an extension mechanism.
Continue reading ISA Wish N°6 – Modern, performant and durableOne of firsts motivation of ISA is to unify the architecture and to make it simple in order to eliminate useless “expertise”.
ISA makes a break with the existent. Thus this architecture is free to make its choices. In other words, compatibility with actual IT is not a concern for ISA. This primary option eliminates the niches for geeks and experts.
Statics and dynamics have pros and cons :
➽ Static often offers the efficiency, an easiest use and the robustness.
➽ Dynamics offers simplicity and flexibility.
An ideal architecture shouldn’t have to choose. It has to incorporate gracefully both statics and dynamics in an unified world.
The first benefit to incorporate security in the lowest layers of ISA is that its safety is generalized every where ISA is deployed, and at anytime. This is a very important advantage when comparing to security problems recurrently occuring on all runtime environments (operating systems, browsers, etc.)
Continue reading ISA Wish N°3 – Intrinsic securisationThe world, the universe is not centralized. They don’t have center. Any attempt to ignore this fact in an ideal architecture will fail.
Distributed computing and storage have to be at the heart of ISA in order to adhere to the reality.
An other aspect of distribution paradigm, implies that the data and treatments are scaling horizontally. Taking advantage of all 4 dimensions of our universe.