Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 6 months ago

Fullstack Personal Finance App|Oauth|Next14|Fastapi|ORM+RAW SQL

postgres, prisma, swr, typescript, next
ifaronti•630
@ifaronti
A solution to the Personal finance app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I picked up a lot of techniques building this app. I was using react context until a fellow dev opened my mind to many techniques for state management without need for overhead costly tools. I also enhanced my sql skills and techniques.

What challenges did you encounter, and how did you overcome them?

I built two backends for this app. One with node/express(Js) and the other with Fastapi(Python). I used raw sql for all the database queries in the fastapi version with psycopg2 then used prisma's queryRaw method for some endpoints in the node version.

The challenge is deciding which orm to use which made me realize that orms are mental drains since they all individually have very distinct syntaxes so I picked Prisma for making database migration and introspecting as easy as

prisma db push for migration

and

prisma db pull for introspecting

No more worries about ORMs when I'm confident with writing raw queries that are SQL injection proof. Plus raw sqls are more performant and can achieve a lot in one query than orms can. Picked up 4 different ORMs and decided never again lol...

What specific areas of your project would you like help with?

***Update. I used docker, ecr and lambda and got the fastapi version of my backend working awesome! check it out on my github ifaronti/finance-backend-fastapi. There's link to the interactive swagger UI docs so you can signup, then use the details to checkout the protected routes.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on ifaronti's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.