Architecture , Design and strategy questions regarding performance . scalability and cost

[tdaly61]

Request Summary:

Not precisely sure how to word this one so please bear with me ....
Does the DA have an interest / responsibility with respect to performance of Mojaloop , scalability and cost of Mojaloop if so can we (the DA) discuss the following questions with James as workstream lead for Performance characterisation

Request Details:

To introduce the topic please see the discussion below from slack (again moved here so it does not get lost)
@James Bush
hey I am looking at the work being done on performance and I see it is being done without kubernetes and it is using k6 for load generation. During the breakout session at the last Mojaloop meeting I distinctly remember a number of things being discussed and I wonder if you can give some context as to what is still happening/planned.
we discussed jMeter for load generation : how come k6 is being used , does it have benefits for the community vrs JMeter ?
strong agreement that the perf harness would be developed to work across vNow and vNext. Is this still the case , reason for asking is that the readme in the ml-core-test-harness repo says "no kubernetes needed"
we discussed being able to create metrics from the perf testing that reported or enabled measurement of cost/transaction but if we can't (easily) run the workload against Mojaloop in kubernetes (mini-loop or EKS etc) then how can we even begin to estimate cost/transaction ?
still on the same "no kubernetes" point , how do do scale out measurements and architecture experiments.
overall is there a plan to be able to test what we deploy ?
Maybe it is just that "we are not there yet" , and I do recongnise that what is there is nicely packaged and simple and has some important utility but concerned that not testing what we deploy always runs significant risks and of course wondering how this applies to a deployed Mojaloop vNext deployment

• Deadline: It would be convenient and efficient to have discussions sooner rather than later (or else we will continue to duplicate effort )
• Impact (Teams): Well performance is really part of "delivery" and delivery really affects all parts of the project
• Impact (Components): again performance along with its implications on scalability and TCO is a broad topic so it will have broad effects.

Artifacts:

• Artifact to consider [@contributor]

Dependencies:

• If Applicable

Accountability:

• Owner:
• Raised By:

Decision(s):

• Approved By:

Details

• Actual decision made as a result of discussion

Follow-up:

• Actions to implement the decisions

[bushjames]

Work is under way on a performance white paper and updates to community documentation. This is currently blocked due to resources being diverted. Updates will be made when possible.