Am glad to hear KOINOS is going for a software architecture framework that provides modularity in itself. As you rightly point out, to reach scalability, one needs to be able to run the software on more nodes than just a single one.
As long as I'm walking around the blockchain space, I wondered why many projects didn't seem to have performance and cost in mind. Since I entered the software industry more than 2 decades ago, I learned what it takes to create reliable, stable and highly scalable software systems. Modularity is key for that. I had the opportunity to work for many years with a company that architected the fastest text message center of the world. It was the fastest back in the 90s, and it is still the fastest. And never ever, the software architecture had to be redeveloped. The sole reason for this was the fact the software framework was architected with modularity and scalability in mind. Though initially it took a lot of development time to set this up, this company benefited for more than 25 years from this. While initially the software was running on a single node, it was d*rn easy to scale up to run the software on 10s of nodes with each node performing a specific subtask. With microservices the modularity increases even more than what was used back in the 90s for this text messaging center, but the concept is the same.
As mentioned, am so glad KOINOS takes the approach of taking the burden to invest more time and effort in building the framework so the chain will be architected in a way it can deal with future performance needs whilst the costs can be controlled and minimised as much as possible. A few characteristics that are required for a blockchains to stay relevant in the longer term.
Interesting example! Thanks for sharing