Yodlee- Transaction Storage -

Yodlee- Transaction Storage -

i'm creating fin app uses yodlee service access user's transaction information. want display info user each time when log in. i'm wondering if app should store transaction info in database after initial successful api query or should app query api each time user log in. can see either way works i'm wondering what's standard way fin app developer uses. , if so, what's advantage/disadvantage?

as mentioned, there 2 ways display transactions user.

1. query api each time , display transactions user.

pros:

you need not have db infrastructure store transactions. easy implement.

cons:

you need dependent on yodlee every time want display transactions user. depending upon how many number of day's/transactions display user, may cause issues response huge depending upon number of transactions user have. in case due network issue app won't able connect yodlee improve user experience questioned.

2. query , store transactions , display local database.

pros:

you can query , store user's transactions , analytic on that.

shouldn't cause issue if user has much more transactions, can set client queries display transactions.

you utilize procedural info extracts maintain info in sync yodlee i.e., have latest data.

cons:

you need implement own transactions reconciliation logic. have setup db infrastructure.

these high level pros , cons of both approaches, while depends upon solution building , how/what options going provide users see transactions in app.

yodlee