"Component Software: Beyond Object-Oriented Programming", 1998
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"
"Component Software: Beyond Object-Oriented Programming"
"Object-oriented programming: Some history, and challenges for the next fifty years"
"Applying Traits to the Smalltalk Collection Classes"
"Self – The Power of Simplicity"
How about this for starters?
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.
First edition uses Component Pascal, Java and C++, with the 2nd edition replacing Component Pascal for C#.