Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 4
    What's the question exactly? Commented Oct 14, 2019 at 13:21
  • What is the volume of data from these metrics? That's going to be a big factor in determining what you use to process them. Commented Oct 14, 2019 at 14:03
  • @svidgen I'm looking for a way to design this system, so any useful design patterns or similar examples are useful. The main problem I have is the extremely tight coupling between main and metric, since a generic metric must have access to everything in main. Also, publishing aggregated data to the users of Main is a problem. Commented Oct 14, 2019 at 15:48
  • @ChuckAdams The metrics themselves are aggregate data. We're talking about averages over time for a few measurements, so it's not a big amount of data to store/process. If it's relevant, measurements are expected about 10-30 times per second. Commented Oct 14, 2019 at 15:51
  • 1
    Personally I'd send the metrics data over a queue and have a separate listener process them. If they need a lot of components from Main, refactor them out of Main into something reusable. It's hard to say exactly how you should build this though without more details on your app. Commented Oct 14, 2019 at 16:41