|
|
|
|
|
|
by paulryanrogers
1339 days ago
|
|
|
Feels a lot like a framework to me, albeit it more by convention and enforced by linters instead of skeletal code. And a fairly rigid one at that. Has this been tested against a more traditional architecture to solve a similar business problem? And if so what were its cons? |
|
|
100% Yes, and the linters are just an experiment I had to see what was possible in terms of "packaging a no-framework framework for distribution".
> And a fairly rigid one at that.
The same problem exists when using a framework. You use the framework's rigid rules and tools or you don't.
> Has this been tested against a more traditional architecture to solve a similar business problem? And if so what were its cons?
I don't know what you consider to be "this" because there's multiple concepts at play in my previous post: (i) "no framework", (ii) the specific "Modular Provider Architecture" ruleset, and (iii) python architecture linter.
What you are looking for in an "against" case? What is a traditional architecture?