Skip to content

Microservice Orchestration framework #5

@VladimirAlexiev

Description

@VladimirAlexiev

@beachtom @rickmakkinga @pasi-paasiala

Management of microservice orchestration mentions:

We use AirFlow in some projects as a data pipelining solution. I don't think it's appropriate for microservice orchestration.

I think FUI should do some research and comparison of such frameworks. A quick google search finds eg:
https://www.tatvasoft.com/blog/top-12-microservices-frameworks/
https://medium.com/microservices-architecture/top-10-microservices-framework-for-2020-eefb5e66d1a2
https://www.geeksforgeeks.org/microservices-frameworks/
https://dzone.com/articles/top-10-microservices-frameworks-for-2023

These open source ones are mentioned in the first article:

We use Spring Boot at ONTO, but I'm not a Java programmer so I don't know exactly for what.


Tom also asked "are there semantic ontologies to describe microservices"

  • I have a folder software,datatype,algorithm,function,execution,provisioning of such ontologies
  • Currently it has these, I recommend checking out the ones marked (*), or I can brief you about them
    ADMS.SW
    CloudInformationModel
    CoCoOn
    CodeMeta
    DOAP-DOAS
    DockerOnto
    EvoOnt
    FNO (*)
    Hydra (*)
    Linked Software Dependencies (*)
    OntoDT
    SWO
  • But I'm not sure either of them coves all that you need to describe Microservices
  • For that, FUI needs to define use cases of what to describe: deployment details? detailed input/output requirements?
  • Then I can look for newer ontologies and research

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions