Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Convert Bot from Monolithic arch to a Microservice based. #115

Open
sr229 opened this issue Oct 3, 2017 · 3 comments
Open

Convert Bot from Monolithic arch to a Microservice based. #115

sr229 opened this issue Oct 3, 2017 · 3 comments

Comments

@sr229
Copy link
Contributor

sr229 commented Oct 3, 2017

This is a backlog issue that we want to agile in a later date.
No, we're not turning Clara into Ayana, reason for this is we implemented a really monolithic system, with the bot being the Kernel with hot swappable modules.

We want to split everything as following:

  • Gateway for bot connections.
  • Core for the actual bot Core (utilities, main class, etc.).
  • cmd for commands.

though not yet planned at this moment, we might consider this arch so the bot can work nominally with a failing core module (for example Core.Preloader failed, but it's suspended already because everything's loaded so operation would continue but reloading would be impossible)

@sr229 sr229 added this to the Backlog milestone Oct 3, 2017
@Ovyerus
Copy link
Contributor

Ovyerus commented Nov 8, 2017

#92 and #121 both tie into this, as they will be separate processes which are interacted with through HTTP (or some similar protocol).

@Martmists-GH
Copy link

Depending on usage, using a custom protocol would be faster and possibly more reliable

@sr229 sr229 modified the milestones: Backlog, 1.0.0 Jan 6, 2018
@sr229
Copy link
Contributor Author

sr229 commented Jan 6, 2018

Assigned to Manic Monika. 0.4x maintenance work should now happen in the respective branch

@sr229 sr229 added Critical and removed backlog labels Jan 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants