this post was submitted on 22 May 2025
29 points (93.9% liked)
Programming
20483 readers
29 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One thing that's common when having multiple sources like different data sources, cms and utility services is having a backend for frontend (BFF) which is what your frontend would call and in turn it would gather all your resources and format it the way your frontend expects it. The bff can cache the more static sources while proxying more dynamic ones.
This might be overkill for your project but it's a nice paradigm when you're dealing with multiple sources or sources that might change.
Yes, I think the problem description fits for moving from static website to having a database and a web service ( with or without javascript, could be just forms, check htmx.org ). For example, if you know Python you could go and check Django. But there are many other ORMs, all aiming to make working with databases easier. Btw, I am not expanding the ORM acronym because it would only add noise. OP should look into that, and understand why these 'frameworks' are called like that... Good luck!