Hi HN,<p>I'm putting together a structure for an MVP, the guts of which should be pretty straightforward(and just using a Flask/React stack). But we're very likely going to target some large enterprises as initial customers. We had a call with our advisors last night, who urged us heavily to use Spring from the start, and that it's important to get the architecture "right" from the start.<p>I've been looking around the internet, and I'm curious if there are any references I could use to ground myself in terms of what they'll require, what the interaction is like, what we should have ready before even showing something to them.<p>Our advisors mentioned that they tend to dig into the architecture, wanted portability for datastores (this was confusing, they mentioned wanting to swap postgres for spanner, for example), understand uptime, security, and so on. Is there some literature/blog post somewhere that I could reference?
It depends on what your business and value prop is. An MVP should demonstrate the ability to solve a problem that a customer would pay to have solved. I'm not sure uptime and security in depth are appropriate for an MVP.or initial discussions.<p>Can you expand on the problem and the user?