Context So you have a typical project with a backend API and a frontend app built with React or Angular. You want to ensure that every time you push changes to production, they are thoroughly tested and deployed. To achieve this, you set up a CI/CD pipeline that handles the building, testing, and deployment processes automatically. At first, everything works smoothly, but as your project grows, you notice the pipeline is taking longer to complete.

People in the tech industry are often criticized for their lack of “soft skills.” I don’t know about other industries, but working in tech, I find this to be true and I’m not immune to this either. A common example of this are online forums (ex: StackOverflow), where developers may swiftly mark your question for closure or down vote it. You’re lucky if they specify the reason for their decision.

Using real-time communication with SignalR allows users to interact with the application without needing to refresh the screen to get updates. This post provides an overview of setting up SignalR in a .NET Core application. In this example, we’ll use a .NET Core API as the backend and Angular as the frontend. We implemented this type of communication on dashboard pages to display workflow status details. Backend implementation .NET Core API After you include SignalR package in your project, register it during startup.