I am asking the question, do we really need bases as it adds a differentiation that I don't think is that useful.
The Polylith documentation here has an FAQ on this
Question: Why not only use components and skip the bases?
Answer: They have different responsibilities. If you start to mix the two, you also lose something. A component has an interface, and is composable. A base has no interface but instead, it exposes a public API. The base is the “base” of your projects/artefacts while the components implement the functionality. This makes it easier to reason about our software.
OK this makes some sense. And therefore in this repo it is only the API that should be a base. I set up the queue and database connectors as bases. This should be changed to be 'Polylith' correct.
I am asking the question, do we really need bases as it adds a differentiation that I don't think is that useful.
The Polylith documentation here has an FAQ on this
OK this makes some sense. And therefore in this repo it is only the API that should be a base. I set up the queue and database connectors as bases. This should be changed to be 'Polylith' correct.