Thanks, I forgot the query engine as a service, and Rongs decision-engine. I am a bit busy coming two weeks, but maybe, when I have time I will publish a micro-service design. I will also follow the discussions and see which already available software is suitable to wrap with a service layer, so that it is possible without writing too much software to create kernel-micro-services, which should work together and replace the less performing pieces by new software. That is one advantage of microservices-concept
Sounds like fun to me, and I already see quite some possibilities in the open source domain. But first we need a plan, architecture. We'll see. Bert Op 16 feb. 2018 14:28 schreef "Thomas Beale" <[email protected]>: > Bert, > > agree, and that's a good list. > > - thomas > > On 16/02/2018 09:59, Bert Verhees wrote: > > I think, it would be good if the community who did this fantastic job, > should also divide a kernel in micro-services and having interfaces between > them, and let there be one entry-service to have the micro-services expose > themselve to the outside world over REST, for now. > > There is knowledge about how to structure micro-services, how which > pattern to sue, between them and inside the service. > > The kernel for OpenEhr is too large for not dividing it. Think about: > - OpenEhr-Terminology, > - Archetype parsing, > - Archetype serializing, > - Storage, > - Validating of data, > - validating of users/authorizations (or connecting to an external > user-service), > - measurement (ucum), > - SNOMED, > - Patient repository (connecting to external) > - Messaging to other EHR eco-systems > - Internal Message queue > > It would be a great help if these microservices were defined, so everyone > could build and borrow them, when they are defined on community level, they > will be interchangeable. > > This is a good starting point for learning about that subject, but an > experienced architect would be welcome. > https://www.packtpub.com/application-development/ > microservice-patterns-and-best-practices > > > -- > Thomas Beale > Principal, Ars Semantica <http://www.arssemantica.com> > Consultant, ABD Team, Intermountain Healthcare > <https://intermountainhealthcare.org/> > Management Board, Specifications Program Lead, openEHR Foundation > <http://www.openehr.org> > Chartered IT Professional Fellow, BCS, British Computer Society > <http://www.bcs.org/category/6044> > Health IT blog <http://wolandscat.net/> | Culture blog > <http://wolandsothercat.net/> > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
