Let's publish a message to the listener from API Controller.public static DelLogMessage LogMessage.public delegate void DelLogMessage( string data)..Add( new MediaTypeHeaderValue( "text/html" )).Global.LogMessage = Requestlog.PostToClient.public static void Register(HttpConfiguration config).In the video below I am capturing an API request and publishing it to SignalR for display purposes. I am using ASP.NET Web API for blog purposes but you can use the same technique for any technology. This led to a thought about SignalR integration with Web API.
With all the above problem statements, I started thinking of how we can visualize/extract what is happening inside the engine room in real-time and with the least possible effort. But in most cases they are expensive if they are easy to use or too complicated to configure as with most of the open source tools. There are ways these log files can be machine read, such as Slack and other tools. If we take on an API build under any technology it's like a black box engine room - the highest level of details about what is happening inside can only be retrieved from the log files. As for any API if the transaction time grows, the life expectancy for the API dramatically falls. In order to execute an API/microservice oriented design we need to be vigilant about the performance i.e., request/response transaction time and logs produced by these components. But with all this agility comes a lot of moving parts, which sometimes results in serious overhead and in some cases failure of the sole product. i.e., the process of transforming an idea into a product. In the new world of APIs and microservices, it is absolutely correct to say that things have started moving really quickly.
0 kommentar(er)
