Open kaioteoi opened 4 years ago
An initial idea of the macro architecture:
How each component is connected to each other?
We roughly have a streamline of information from input to output with some processing in the middle. The main components that might require some effort are Insert API
and Search API
.
Can those be grouped on subdomains?
Yes. In the diagram they're represented as two macro groups Inbound
and Data platform
, there's even more options of grouping to be explored within each subdomain.
Can we break up those subdomains into separate services? Or keep'em together?
There's no explicit reason for keepin'em together. We have clear responsibilities for each domain.
What other non-functional components are associated with the platform? (content crawling, security, authentication)
Content crawling
was specified as one of the inbound processes. Security
and authentication
are topics that can be discussed in the future without any drawbacks of not deciding anything so early.
[Optional] Shall we discuss about the Design as well? (e.g: UI wireframes, color palette, sound design, visual component base styles)
This discussion can occur in parallel to the Domain discussion, not here.
As per #3, roughly the main features of the platform will be:
Edit: changed from API to Service, as the component doesn't have to be necessarily a API to fulfill the purpose.
Context
Detail
The scope of this Issue is to answer the following questions:
Comment
,Author
,Post
)