I have been assigned to a project where the end-product is a website as a music community. So it's uploading of music, sharing it amongst other users, listening to music from the website and so forth. It's a project that will not cross the borders of this nation, that's certain, so the scaling part is really not interesting.
At the moment we have ~12.000 users total, so it almost nothing.
That being said, for me it's a really simple and straightforward product. But we all know that simple can be ruined by a lot of things.
My problem with the codebase is the many obscure layers. We start of by loading a "shell" and from there we do like this:
HTML/AngularJs -> TypeScript -> Breeze -> WebApi/OData -> Entity Framwork
So really, my question is whether it's just me or if I am correct in my mind when I think this is totally over-architectured. And has someone else has seen an architecture like this and would you agree that cutting away the typescript + breeze abstraction would be the way to optimize the architecture ?
Having seen something like this I have lost some faith in TypeScript, because it is really hard for me not to see it just an abstraction between connecting some frontend framework and some backend framework, instead of them just "talking together" with TypeScript in the middle.