It is a bit hard to just explain in a bunch of comments.
In your examples you need to add extra layers, just like you would do with the microservices.
There would be the DTOs that represent the actual data that gets across the models, the view models that package the data together as it makes sense for the views, the repository module that actually abstracts if the data is accessed via SQL, ORM, RPC or whatever.
You should look into something like:
"Domain-Driven Design: Tackling Complexity in the Heart of Software"
This was the book that defined components https://smile.amazon.com/Component-Software-Beyond-Object-Or...
At the time components were going to be the next level above objects - they were the black box that contained a lot of objects and provided a nice programmer interface. Unfortunately the ideas seem to have disappeared, Delphi is an even better example of a component model than VB was imho.
Which is ironic, given that people tend to forget that it was C++ which made OOP mainstream, there wasn't any Java or C# back then, two fully OOP based languages.
The other part is that component oriented programming is actually a branch of OOP, from CS point of view, with books published on the subject at the beginning of the century.
https://www.amazon.com/Component-Software-Object-Oriented-Pr...
The first edition uses Component Pascal instead,
https://www.amazon.com/Component-Software-Beyond-Object-Orie...
Then even if it hasn't taken the world by storm,
"Designing Object Oriented C++ Applications Using The Booch Method"
https://www.amazon.com/Designing-Object-Oriented-Application...
Assuming you also feel like reading about UML design stuff
"Object-Oriented Analysis and Design with Applications"
https://www.amazon.com/Object-Oriented-Analysis-Design-Appli...
"Component Software: Beyond Object-Oriented Programming", 1998
https://www.amazon.com/gp/product/0201178885
"Component Software: Beyond Object-Oriented Programming", 1998
https://www.amazon.com/gp/product/0201178885
"Component Software: Beyond Object-Oriented Programming", 1998
https://www.amazon.com/gp/product/0201178885
In your examples you need to add extra layers, just like you would do with the microservices.
There would be the DTOs that represent the actual data that gets across the models, the view models that package the data together as it makes sense for the views, the repository module that actually abstracts if the data is accessed via SQL, ORM, RPC or whatever.
You should look into something like:
"Domain-Driven Design: Tackling Complexity in the Heart of Software"
https://www.amazon.com/Eric-J-Evans/dp/0321125215
"Component Software: Beyond Object-Oriented Programming"
https://www.amazon.com/Component-Software-Beyond-Object-Orie...
"Object-oriented programming: Some history, and challenges for the next fifty years"
https://www.amazon.com/Component-Software-Beyond-Object-Orie...
"Applying Traits to the Smalltalk Collection Classes"
https://rmod.inria.fr/archives/papers/Blac03a-OOSPLA03-Trait...
"Self – The Power of Simplicity"
http://media.cichon.com/talks/Introduction_Self_Language_OOP...
https://blog.rfox.eu/en/Programming/Series_about_Self/index....
How about this for starters?
"Component Software: Beyond Object-Oriented Programming"
https://www.amazon.com/Component-Software-Beyond-Object-Orie...
https://www.amazon.com/Component-Software-Object-Oriented-Pr...
The other part is that component oriented programming is actually a branch of OOP, from CS point of view, with books published on the subject at the beginning of the century.
"Component Software: Beyond Object-Oriented Programming"
https://www.amazon.com/Component-Software-Beyond-Object-Orie...
First edition uses Component Pascal, Java and C++, with the 2nd edition replacing Component Pascal for C#.