Code encapsulation is the most useful aspect of Object Oriented Programming. It allows to define specific functionality in one place, it bundles data with its functionality, it prevents unexpected modifications to object data by external code, and it facilitates cooperation between programmers working on the same project by letting them use each other\u2019s methods without knowing the object\u2019s internals.<\/p>\n\n\n\n
Spiderwiz takes the encapsulation idea one giant step\nforward. Instead of code that is encapsulated in objects that refer to each\nother through methods, the interface is the objects themselves, strictly\nself-contained. A change in the object is broadcast when the object\u2019s commit()<\/a> method is called, and the change is\nhandled by implementing the object\u2019s onEvent()<\/a> method. The same object type can have\nmultiple functionalities, each of which is encapsulated in a different\nextension of the basic object.<\/p>\n\n\n\n Moreover, beyond encapsulating functionalities in objects,\nSpiderwiz facilitates the isolation of each object implementation in its own\nbuild unit. Build units interact with each other over a network in a way that\nis completely transparent to the programmers. Regardless of whether object\ninteraction is inter-process or inter-service, programmers would write exactly\nthe same code. For explanation how it works see our blog post Lean and Mean\n\u2013 Under the Spiderwiz hood<\/a>.<\/p>\n\n\n\n All this implies that Spiderwiz is an ideal platform for\nbuilding systems of microservices<\/em>\nthat interact in a service mesh. Actually, as every object\u2019s implementation can\nbe put in its own service, we can call them nanoservices<\/em>.\nWhatever is the name, the measureless benefits to developers and system\nadministrators are apparent.<\/p>\n\n\n\n