I think there are quiet a lot more out of the box implementation especially
using Cloud services like AWS Lambda and ApiGateway.
There is also a concept of Backend For Frontend (BFF) which would also be a
smart way to allow any frontends to access the backend.
Here's some resources on BFF:
I'm not sure what exactly this thread is about (and don't know what "my
original post above and Juhan's specific thinking" refers to, link?), but
while glancing over this was just wondering if by "proxy" you perhaps would
be interested in one of the "API management" solutions out there?
Stuff
Thank you Victor. +1 on the contribution of the proxy.
I look forward to seeing the Pull Requests in the appropriate places.
Do you have some high level flows for documentation of this approach to put
on the wikis?
For everyone's benefit, BIAN is the Banking Infrastructure Architecture
Network
Hi,
We have been working in a proxy using node.js and has been deployed to
firebase, but any capable node.js server could be used.
Mobile wallet <-> proxy <-> Mifo's/Fineract APIs
We have used the proxy to accomplish the goals to be aligned to BIAN 4.0 and
OpenBanking Mexico usability
Devs - I would like to resurface this discussion. Please see my original
post above and Juhan's specific thinking.
(direct) Channel access without a middle-layer or proxy of some kind is not
recommended in production.
By implication, anyone building a front end app that is aimed at end users
