refactoring module layout of project about horreum

[rvansa]

Hyperfoil report is closely tied to Hyperfoil itself, so it makes sense to keep it separate from Horreum which is supposed to be generic.
But what about alerting? IMO it would make sense to have both storage (current Horreum) and alerting/regression under single UI. Then it'd be convenient to have 3 modules: storage and alerting backends and UI frontend, within single repository.

[rvansa]

@johnaohara ping?

[johnaohara]

@rvansa sorry, completely forgot about this. Should we separate out alerting into a separate module, or just build it into the existing backend/frontend? Do we envisage Horreum to be modular? I think creating a modular architecture would add another layer of complexity. I think that we either have alerting completely separate (which implies a seperate GUI), or we bake it into Horreum, leaving Horreum as a single module project with data storage and reporting in one GUI

[rvansa]

'Modular' sounds really too generic, and I have no idea how should modular React apps look like. All I am saying is that two UIs would hurt UX in my view.
I don't have a problem with backend separation if someone thinks that it will make it less of a spaghetti project. I don't have a issue with serving the UI from one container and running the backend(s) in another. But I haven't invented microservices either, my current stance is rather neutral.

[rvansa]

@johnaohara Any further comments? Will you make the decision or should we do a poll?

[johnaohara]

@rvansa as discussed
"lets do this, single application containing storage, alerting and unified UI, the storage and alerting have different URL paths, and if we need to split later it should be possible"

[rvansa]

I've pushed the changes, along with the package & some properties rename.