Re:Rails on OCaml
by scotty79 on Wednesday March 20, 2019 @02:48PM
(#19445471)
> ... Java’s anemic type system (which forced complex class hierarchies where, in dynamic languages ...
It just occured to me that relationship between Java and more expressive languages that do more, parallels relationship between microservices architecture and monoliths.
Because in Java it's hard to make smart classes that do everything you need, you need to create whole ecosystem of dumb classes that only through their interaction are capable of doing what you need. But the language has no tools to deal with interactions between classes. For monitoring them and reshaping them just as there's no tooling in microservices architecture to deal with complexities of inter-service interactions.
So in theory you have nice isolated units that should be easy to change and swap. But you just pushed the complexities of your problem to in-between of your units where they are no longer well visible and very hard to manage and evolve.
It just occured to me that relationship between Java and more expressive languages that do more, parallels relationship between microservices architecture and monoliths.
Because in Java it's hard to make smart classes that do everything you need, you need to create whole ecosystem of dumb classes that only through their interaction are capable of doing what you need. But the language has no tools to deal with interactions between classes. For monitoring them and reshaping them just as there's no tooling in microservices architecture to deal with complexities of inter-service interactions.
So in theory you have nice isolated units that should be easy to change and swap. But you just pushed the complexities of your problem to in-between of your units where they are no longer well visible and very hard to manage and evolve.