RepoDb is a new hybrid micro-ORM library for .NET, designed to cater the missing pieces of micro-ORMs and macro-ORMs

RepoDb is a new hybrid micro-ORM for .NET designed to cater the missing pieces of both micro-ORMs and macro-ORMs (aka full-ORMs). It was also designed to simplify the micro-ORM coding experience and at the same time maintaining the performance and efficiency of the application.

When I first started playing with API testing in .NET Core 3, I wanted to have a quick In Memory API test that takes snapshots. In this article, I am going to describe a way how to do it easily so even you can do it in your project. If you are not familiar with the snapshot testing and why you should care, it will be explained below.

Sooner or later, when developing an app in the real world, you will need to share variables with different components, as well as preserve their value even when changing the displayed page. Passing variables between components or pages with parameters is not the best solution in complex situations. There are various ways to solve this issue, and in this post we will see how the Model-View-ViewModel pattern can be used for state management.

A number of high profile Twitter accounts, including Bill Gates, Elon Musk and Apple, were breached on Wednesday. The verified accounts for Gates, Musk and Apple issued tweets promoting a cryptocurrency scam, asking followers to send money to a blockchain address in exchange for a larger pay back.

Code review is a process and it’s evolving. It’s like every skill that we need to train in order to be better at it. Those 10 tips can help you improve code review process in your organisation.

Resolver is an interface that class can implement to be a data provider. Resolvers are useful when there’s a component displaying data in the same way, but the data itself needs to be different based on path.

This article presents an alternate way for standard filtering with Where LINQ extension. The result is query has similar performance (perhaps slightly better). But the most important, it doesn’t time out due too many filter parameters.

Dockers aren’t really a new thing around, but in many cases developers are spending time to create proper image or trying different Dockerfile configurations, or simply they don’t pay attention to re-usability and multi environment build.

Consider a Kubernetes cluster with 3 worker nodes having a memory of 10GB each. Suppose the developers end up deploying some pods by mistake which consumes almost all the cpu and memory available in the node. Hence causing resource contention in the others application pods which serves traffic from consumers. This could also be caused when hackers inject high resource consuming pods intentionally into the system.