Adding support for integrating analysis modules as micro-services

[kavehtp]

Thanks for developing this amazing piece of opensource software. It has helped us a lot and we are actively using it as the basis of our UI.

One of the features that can add a lot of flexibility to HistomicsTK is to support addition of analysis modules as micro-services. Apart from python modules, we have a few other modules that are written in C++/Java/Lua and integrating them with HistomicsTK is not straightforward. Having a protocol (or a template) for integrating such modules can be a big advantage, IMHO. Even current analysis modules can also be framed as independent micro-services and this can improve a few things, such as faster build process for the main HistomicsTK plugin.

Please let me know what you think and whether there are any similar plans to enhance HistomicsTK's modularity. Once again, thank you all for your great work.

[dgutman]

We have item tasks that do something similar.. I am doing something similar but it's hard to figure out how to make this completely generic..

…

On Tue, May 28, 2019, 11:01 AM Kaveh Taghipour ***@***.***> wrote: Thanks for developing this amazing piece of opensource software. It has helped us a lot and we are actively using it as the basis of our UI. One of the features that can add a lot of flexibility to HistomicsTK is to support addition of analysis modules as *micro-services*. Apart from python modules, we have a few other modules that are written in C++/Java/Lua and integrating them with HistomicsTK is not straightforward. Having a protocol (or a template) for integrating such modules can be a big advantage, IMHO. Even current analysis modules can also be framed as independent micro-services and this can improve a few things, such as faster build process for the main HistomicsTK plugin. Please let me know what you think and whether there are any similar plans to enhance HistomicsTK's modularity. Once again, thank you all for your great work. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#661?email_source=notifications&email_token=AAFODTWKNTOY26PDNQMCVSDPXVQNJA5CNFSM4HQFK4K2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GWI7TBQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFODTXMF3NL7WLG62M6IR3PXVQNJANCNFSM4HQFK4KQ> .

[manthey]

There are several approaches to this, and I expect we'll eventually make a way to compose efficient workflows between containers with small services. Several clear, specific use cases will clarify which approach makes the most sense.