Hello guys. The time has come for us to take the first step in architectural assessment: the definition of the mission. Basically we have to decide here what is important in Marvin and what is outside the scope of the project. This is important because, during this analysis and the development process as a whole, we will be able to segment what is really important and make things more simple and functional. Also, if it looks cool, we can include that on the Marvin-AI homepage.
As stated earlier, I will post an initial draft and would like to receive your feedback to complete a few points: The Apache Marvin-AI platform aims to offer: - a practical and standardized solution, - for the development and deployment of machine learning applications. Aiming to offer the user: - scalability, - language agnosticism, - standardized pipeline (DASFE), - possibility of remote versioning of artifacts. Does anyone have any suggestions for more important features, resources or design decisions in Marvin? Thank you very much, Lucas Cardoso
