Do you mean full-stack, backend, phone app, or what? The questions seem too general to have answers–they’re pretty much all, “The right frameworks / patterns / libraries depend on what you need to get done.”
Fundamentally, museums aren’t terribly different from anything else that has users and needs to keep track of stuff and provide a pretty front end for users to do stuff. You want a database layer, a web server with integration with payment processing, and so on. There really isn’t anything Scala-specific at that level.
If you understand the application space well enough to start asking specific questions like, “How can I use Scala to maintain a membership database with atomic commits and rollbacks–I want to adhere to ACID principles,” then we will probably start saying things about doobie over PostgreSQL if you or your favorite LLM is willing to go with the CE3 stack; and we might mention Slick if you’re wary of the programs-as-values paradigm.
But first you need to do the non-Scala work of understanding full-stack development, because I think that’s what you’re getting at. Once you understand what even is all this stuff, then you can start to think about choosing languages and frameworks and stacks and so on, and ask sufficiently precise questions so we can give insightful answers not just, “Um, yeah, do the thing–that thing you’re doing. Yeah, you can do it in Scala. Once you nail down what it is.”
Or you can just throw the whole problem at your favorite frontier LLM. It might get somewhere! It will probably have security holes! But while it’s doing it, ask it to tutor you in each part, so that after it’s done, and it does or doesn’t work well enough, you have a better understanding of the problems space and why it really has very little to do with museums at all (at least as you’ve described it).
Or you can just use Spring / Spring Boot with Java. It already has something for almost every conceivable need, especially backend. If you want a pretty front-end, you’ll probably need a bit more.
If the question really means, “Does Scala have a Spring / Spring Boot megalith equivalent”, the answer is: no, not really. There are pieces that work well, and can work well together. You do have do know what you’re doing. (You do with Spring, too. But you can choose Spring before you have any clue what you’re doing, because it covers practically everything.)
