In a recent interview I was told a new backend was needed to fascilitate a frontend application's need for a quiz-like app.

Shoot yourself in the foot? Andere beeldspraak? in your current solution... ask yourself, do you really need your backend? - what am i persisting? do i really need that? - how dynamic is my content? - how big a % of my users actually needs a session? Some downsides of dynamic solutions include - setting up and maintaining a database cluster - backups - consider your time-to-market For high traffic / high available solutions this includes - setting up load balancers, handle sticky sessions / round robin - caching solutions, which creates .... - penetration testing - load testing # static site generators et al. # seo your service might need server-rendered pages too... Think outside of the box... Traditional webstacks are ... In a time of serverless developments....

Do you really need that backend?