10 hours ago, WhatDoYouMean wrote
You said it better than I could have ever done it.
OK so, go with an SOA architecture. Take the best of what's known today.
1) Database access code these days is generally automated by ORMs and generated for you at the press of a button. .NET has ORMs, Java has ORMs, Rails has ORMs, even PHP has ORMs and the implementation of the Active Record pattern (although there's an argument that active record is a silly pattern anyway). So database access code doesn't matter.
2) If database access code doesn't matter then you could use that as your model. It's not idea, it probably passes too much information to the web pages that they don't need though, the idea would be having a layer that turns the database models into the information that each part of your application actually needs - view models.
3) Creation of view models from models is usually a simple object mapping, pretty easy to write. .NET has projects like automapper that take care of it for you, but if you want to write the code yourself for some reason it's usually a property to property mapping done in a constructor.
4) If you want to plan for an unknown future the current trend is to just JSON to pass to layers, so your database feeds through to your application via a JSON layer. Again there's generators in the major languages to do this, or if you want, it's just writing out text from input.
So yes, you could spend 6-9 months writing this stuff yourself because you want to keep yourself in a job, or because you think you're going to migrate to something else in the future. The thing is you always migrate at some point 5 years down the line. By adopting patterns and tools that aid you and remove the need to write code you're going to make your migration easier not harder, because the tools (model binding, ORMs, etc.) all exist in the major (and most minor platforms). Plus of course they're well written and well tested, so you can have confidence they work, which, to be frank, doesn't exist for a long time when you reinvent the wheel yourself.
My smart-* marriage comment (which I borrowed from someone else, because their responses if they respond would tend to be more sane than mine ever are) still stands. Do you look at your personal relationships with the attitude of planning to get out because something better may come along in a few years? I hope not, because if you do that you aren't ever going to be happy, and you're going to spend more time looking at other options than working on and getting your current relationship/platform to work.