Introduction MySQL is well known for Enum data type with some predefined values. If we try to insert or update any custom values, we will get exception. Coming to MSSQL we will not have any equivalent data type for MySQL Enum. In monolithic architecture-based applications, it is fine to have code based Enums inside the applications and store their values in database TINYINT data type fields since we will have business layer as intermediate between presentation layer and database layer. We are in new era of microservice architecture-based applications. It is not good to have Enums inside the code base since single application may have fine grained services and each service will have their own domain layer. In such cases we may need to duplicate the code based Enum inside service which may bring maintenance nightmare. For this problem we will introduce the look-up tables as solution which will act like Enum, and it will have its own key-value pair records. Sample Use Case Let us
Introduction We are in the new world of microservices and cross-platform applications which will be supported for multiple platforms and multiple heterogeneous teams can work on the same application. I like ASP.NET Core by the way its groomed to support modern architecture and adhere to the software principles. I am a big fan of dot net and now I become the craziest fan after seeing the sophisticated facility by dot net core to support infrastructure level where we can easily perform vertical and horizontal scaling. It very important design aspect is to keep things simple and short and by the way, RESTFul applications are build and it is a powerful mantra for REST-based application and frameworks. Some times we need to overrule some principles and order to handle some situations. I would like to share my situation of handling HTTP long polling to resolve the ASP.Net core 2 mins issue. What is HTTP Long polling? In the RESTFul term, when a client asks for a query from the serv