Onion Architecture and LENR (Axil Axil)

The following post was submitted by Axil Axil

Like electricity and electronics, we are at the Benjamin Franklin stage of our understanding of LENR as a technology. We stand in a field with a kite string in our hand with a kite lifting into a thundercloud.

The innovation and insights of Maxwell are still many years off, the simple knowledge that allows an electrician to do his job is still not yet defined. The nature of the electron is not even imagined. The transistor and the technology of solid state systems is centuries off into the future.

Like electronics, LENR will require a onion layer approach to education. Complex technologies cannot be swallowed in one mouthful.

Such complex fields of knowledge is of a specific type of architecture I call “Onion Architecture”. I’ve found that it leads to more maintainable applications since it emphasizes separation of concerns throughout the system. I must set the context for the use of this architecture before proceeding.

Like software and computer hardware design, It emphasizes the use of interfaces for behavior contracts, and it forces the externalization of infrastructure. Here there is a requirement for a traditional layered architecture. This is the basic architecture I see most frequently used. Each subsequent layer depends on the layers beneath it, and then every layer normally will depend on some common infrastructure and utility services. The big drawback to this top-down structure of knowledge, is that the detailed fundamental layers are incomprehensible until the top most layers are understood.

If someone were to reveal the ultimate cause of LENR, it would not be understood until all the upper layers were understood. This is why getting control of LENR will take many years of exploration and education as each layer of the LENR knowledge base is put into place.

Axil Axil

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies.