First off I've got some work on the bench (phsyical PC repairs) to clear before I can toss together a quick standalone of a full static that's "vanilla" enough. I could just toss up an existing site, but I'd rather "dumb down" and use more verbose code to explain it clearly.
A couple pages would be sufficient to start. My point of discussion is how well your proposed architecture would scale to a large/very large site/application and what problems their may be and your solutions to those problems if any.
Which is why I'm interested to hear what you think, becuase I HEAR that claim a lot, that there's some sort of BS about it "scaling large" that is a "wah wah, it is because we say" that I never hear backed by a single fact or logical/rational thought. If anything, routing crap is oft so complex -- or at least what I encounter people calling routing -- it's THAT which is the slow, bloated, hard to maintain mess... because it's more code, and an attempt to shoe-horn every request into a single programming model, without simply using the request itself AS the model. If that makes any sense...
One reason I was hoping to see a crud application is that it contains "standard" complexities of most web applications and would surely be part of a large website/application.
Which to me sounds like over-complex over-thought answers to simple problems. Hence why most codebases where people call it "CRUD" or talk about "Routing" seem like two to ten times the code in as painfully and pointlessly complex a manner as possible.
My initial position is that I would agree that your architecture would be fine for a small to medium site/application but I believe it would be problematic for a large scale application.
Whereas if this is for a website, the term "large scale application" shouldn't even apply, and reeks of bloated inefficient crap that probably tells large swaths of users to go **** themselves. The attitude I hold towards 90%+ of the things people are calling "web applications" right now. Utter and total shite that does more harm than good to clients and often why I get called in to fix things in the first place!
I think we're light-years apart in mindset and mentality when it comes to solving client's problems -- or we're simply dealing with different problems from the start.
Hell, my response to the proposal request would probably upset you, as it's part of my client filter.
I find some statements and questions in your request troubling, as it indicates the possibility you have overthought and overscoped your project without actual planning or concern on what it is you really want to do. The lack of information of intent makes it difficult to even come close to putting together a proper proposal.
In particular, the use of marketspeak doubletalk such as "large to very large enterprise website application." indicates that you are likely going to be building systems that alienate large swaths of users, either through a lack of focus, pointless layering of shortcuts, or just plain accessibility failings. The concept of a "website application" has become near synonymous with telling visitors to websites -- particularly those with accessibility needs -- that they are not welcome, and to that end I would require very specific details on why you think you need an application and what the data is.
Much less that since I also work both as an accessibility and efficiency consultant, the mere use of the word "application" and "website" in the same sentence indicates a failure to grasp what websites are and/or are for.
Same for the "project our size" notion where most of the time even the "largest" of projects shouldn't be that "large". If they do end up so, it is typically through developer ignorance, incompetence, or ineptitude. Simply put, people making websites who have no business even being involved in the process.
As to your staff not being technically oriented and/or ease of updating and maintaining? If this is a multi-million dollar project FLIPPING HIRE SOMEBODY!
In fact, that statement alone is making me considering rejecting your request.
With all due regards,
Jason M. Knight
Paladin Systems North
... and I have sent replies to potential clients that read exactly like that. You have all the telltales in there of people who aren't worth the headaches or time of working for.
Just like how the reply to the most recent proposal I sent to a company had me kick them to the curb as they were willfully negligent which is what got them in trouble in the first damned place, and then were willfully fighting of the necessary changes to get them out of trouble. So I willfully told them to hit the bricks until they were willing to make the changes to stop them having their arse sued off.
And they too had this "large enterprise website application" bullshit over something as simple as a flipping banking portal.