[
https://issues.apache.org/jira/browse/FINERACT-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053189#comment-18053189
]
Aira Jena commented on FINERACT-2439:
-------------------------------------
I'm interested in building this Self-Service API (BFF) component. I've been
actively contributing to Fineract and have done a deep dive into the codebase
architecture.
My understanding of the requirement:
* A standalone Backend-for-Frontend service exposing consumer-facing APIs
* APIs for: account balances, transactions, loan applications
* Secure authentication for end-users (separate from admin Fineract users)
Proposed architecture based on Fineract patterns:
* Standalone Spring Boot 3.x microservice (following the modular pattern of
fineract-client)
* Call Fineract backend via HTTP client (using existing API patterns)
* JWT-based consumer authentication (similar to AuthorizationServerConfig but
for customers)
* Follow CQRS principles with proper command/query separation
* JAX-RS/Jersey for REST endpoints (consistent with fineract-provider)
A few clarifying questions:
* User Model: Should consumer users be stored in Fineract's existing m_appuser
table, or should this BFF maintain its own customer identity store linked to
Fineract clients?
* Multi-tenancy: Should the Self-Service API support Fineract's tenant
isolation (passing tenantId to backend), or is this POC single-tenant?
* Repo Location: Should this be a new module in the apache/fineract repo (like
fineract-self-service-api), or a separate repository under apache?
I can deliver an initial architecture design doc within some days. Looking
forward to your guidance!
Thanks, Aira
> Create a new backend for front end component POC
> ------------------------------------------------
>
> Key: FINERACT-2439
> URL: https://issues.apache.org/jira/browse/FINERACT-2439
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: James Dailey
> Priority: Minor
> Labels: GSOC, gsoc2026, mentor
>
> h3. *Build a Self-Service API Component that Connects to Apache Fineract*
> When the project removed self-service APIs in 2025, it did so understanding
> that we would need an outside component to make that connection as part of an
> overall solution.
> This project is to create - as a Proof of Concept (POC) - a new dedicated
> Self-Service API component or service that integration with Fineract backend.
> It will need to expose APIs to consumer facing applications for typical
> activities like viewing account balances, transaction initiation, loan
> application, etc.
> The idea is for GSOC candidates to propose a design and build the POC.
> Minimal criteria include testing, authentication methodology, documentation.
> Not included in this GSOC would be the end consumer APP, although that may be
> undertaken by another project and coordination would be needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
