As the world of the “new normal” emerged, WebRTC-based software has reached almost every corner of human life. The business world has also been affected by this change, meaning that without WebRTC, almost every modern business would mostly not be possible.
While developing an enterprise app for one of our clients, we encountered a rather interested requirement requested by the end users – to reduce the number of user accounts required. Identity Server turned out to be the best solution.
Even though WebRTC is simple to implement and use, not all real world use-cases are that straight-forward. WebRTC has the solution for those cases as it covers almost any complex request that comes across, and that’s why it is and will stay the technology to go for in modern web-based real-time communication systems.
We are moving from theory to practice by building a powerful and secure WebRTC solution with Microsoft SignalR (with .NET Core 3.1) as our socketing & backend choice, and Angular 11 as our frontend client choice.
“Twas a long time ago, longer now than it seems, in a place that perhaps you’ve seen in your dreams. For the story that you are about to be told.” – Danny Elfman, Nightmare Before Christmas
When implementing an API using ASP.NET Core, there’s often a need to authorize that API’s users. Your system might be organized into several separate areas, which provide access to different resources and actions. It’s very likely that not all users are allowed to use all of those areas. Within a single area, a design might require restricted access to data…
Front-end testing is the testing of the functionality and usability of an application, including its graphical user interface (GUI). Because Angular is a TypeScript-based open-source front-end web application platform, you should be able to test it.
In the world of web applications, everyone loves the scenario where one app requests an action and another app responds to that request afterward.
