Service Fabric

Logging is hard, especially in microservice world. Fortunately, not with service fabric as it's trivially extendable to meet our complicated needs. In my latest journey I needed to track log requests across multiple microservices calling each other via Service Remoting. There is no easy way to do it

While developing new solutions, we often use Service Fabric services as controllers.  Executing actions on demand, checking the status of other Azure services, running maintenance routines, cleaning up data, the possibilities with Service Fabric are endless.  Often, that means we have a clust

In one of our Service Fabric services, we host a TCP socket to feed data into another system. The implementation is simple, using a regular TcpClient to accept listeners and read and write to them. As part of the behaviour of this socket, we listen for an initiation command after connecting. To

We have been working on integrating a TCPListener written in C# within Azure Service Fabric enabling the streaming of raw data off an Event Hub and back to a socket. The main advantage for this apart from giving the customer a more flexible approach to development and testing is that it made our lif