Architectural Guidance
-
We're a small internal dev team and we have an .NET & AngularJS web site, except the site is supposed to act as a host of other sites/applications. So the users go to a single address, they can then get to the other apps via a dashboard, but the core site handles the 2 different authentications (windows and custom oracle database based) and other common features. Currently the .NET side is all separate projects for each app. The AngularJS is just one app. Ideally we'd want the applications to be more independent, so that we could update one and be comfortable saying that regression testing of the others isn't needed. Some guidance on: How would you design the web side? I was thinking separate angular apps with the 'host' site using iframes? As I couldn't think of another way to keep the whole look and feel with out code duplication. The authentication, its OAuth/Owin, the windows AD and Oracle are separate, but the same user could have creds for both. We've currently got two 'client_ids' in the single web app, which doesn't seem right, as I'm tracking two access_tokens. I'm thinking I could use OAuth claims instead. We are also planning rewriting from AngularJS, would anyone recommend an alternative framework? I'm half thinking of Blazor, to reduce the number of languages the team needs to know, but obviously its still new, so the amount of resources about and its long term viability are risks. Apologies for the rambling post:)