-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: architecture armonik extension development #46
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This AEP is a bit short compared to all the sections from our list of sections. As it describes our high level sdk, it is not really linked to our model.
I expect some of the following subjects to be addressed:
- Not rely too much on C#. (especially some namings)
- Some examples to show how it is expected to be used. How do I define a task ? How am I expected to get my output ?
- What is a task ? a result ?
- ResultService should not appear as we want to rename to BlobService or some other thing with a clearer meaning.
- How do I monitor things ? What can I know and how ?
- Worker side has not been adressed yet (I now it is not for now) but I would expect a few words about it.
- SDKs should provide ways to easily define ArmoniK based applications (client and worker side). I think this should appear in the abstract and motivation parts. Why do we want that should appear too.
AEP/aep-00004.md
Outdated
|
||
This AEP aims to create a standard architecture for ArmoniK's extension development. It proposes services decoupling, segregating interfaces to related domains, and enriching domains. | ||
|
||
# Proposed Solution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proposed Solution is not a section available in our template. See AEP1.
No description provided.