rygh4775
commented
5 years ago Scope the problem
- A user account with multiple back accounts.
- It pulls Financial history. (outgoing/incoming/current money)
- Each payment transaction has a "category". (food, travel, clothing, etc.)
- Users can re-assign the category.
- Users will use the system to get recommendations on their spending. (sholdn't spend more than X%)
- Email notifications either on a regular basis, or on certain conditions.
Make Reasonable Assumptions
- Adding or removing back accounts is relatively unusual.
- The system is write-heavy.
- The typical user makes several new transactions daily, although few users access the website more than once a week.
- Their primary interaction might be through email alerts.
- The banks probably won't push data to our system.
- Alerts on users exceeding budgets probably do not need to be sent instantaneously.
Draw the Major components
- Categorized transaction datastore
- Budget datastore
Bottleneck
- categorizer and budget analyzer with lots of transactions coming in at once.
- Group the transactions with a lot of duplicates across the sellers.
- Group the transactions with a lot of duplicates across the sellers.
Personal Financial Manager: Explain how you would design a personal financial manager (like Mint.com). This system would connect to your bank accounts, analyze your spending habits, and make recommendations.