Git Product home page Git Product logo

Comments (7)

sara-02 avatar sara-02 commented on August 10, 2024

@msrb Going forward we might add more components under the analytics_platform folder, one of them is a WIP PR #2 . So are you saying that each of those components should have its own repo?

from fabric8-analytics-stack-analysis.

msrb avatar msrb commented on August 10, 2024

Hey Sarah,

So are you saying that each of those components should have its own repo?

It depends... if you don't share code between the components and if you expect to have a separate Docker image for each of them, then I'd say it would be better to have them in separate repositories. But if things are more complicated, then it's up to discussion :)

from fabric8-analytics-stack-analysis.

vpavlin avatar vpavlin commented on August 10, 2024

I second Michal's suggestion - if there are 3 images - i.e. 3 microservices - it would be best to split into 3 repos. If there is any shared code, that should be also split out into a library.

from fabric8-analytics-stack-analysis.

tuhinsharma121 avatar tuhinsharma121 commented on August 10, 2024

Yes. I completely agree with you guys. While we started this project we believed that keeping 3 microservices would be useful from PGM perspective. But later on we realised, there are only 2 potential microservices as KRONOS and JANUS [WIP]. GNOSIS, SOFTNET and KRONOS are tightly coupled as for the training part they need to be invoked sequentially on AWS EMR (It will be quite troublesome to keep track of the ending time for each training job for respective components) while there is only one user facing service which is KRONOS. I am working on making only one service KRONOS out of these 3 services. Please share your thoughts.

from fabric8-analytics-stack-analysis.

miteshvp avatar miteshvp commented on August 10, 2024

+1 to Michal and Vasek here. Tuhin make sure if there is a shared codebase that can be used across multiple different services, should be moved under a separate repo as library. Rest I agree with one service for KRONOS currently so one repo is enough.

from fabric8-analytics-stack-analysis.

tuhinsharma121 avatar tuhinsharma121 commented on August 10, 2024

Created #7 .It requires some more iterations though. We can keep this issue open and revisit this later. Please share your views.

from fabric8-analytics-stack-analysis.

msrb avatar msrb commented on August 10, 2024

Thanks @tuhinsharma :) please feel free to close this issue 😉

from fabric8-analytics-stack-analysis.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.