2 ms·

I disagree with that - what i’d call a plugin architecture - leads to a very nice separation of components.

• interactivecode 5y ago
  plugins works for things that are plugins. Most people seem to equate separation of concerns with everything should be a plugin. Otherwise you get massive issues actually working across each plugin (or package). So unless your component is actually used in multiple core products it's not a component, it's just a part of your monolith. Making it a separate component usually, just spreads your monolith across several git repo's