Different people define Entity, Model, ViewModel and DataModel in different ways. However, these terms may sometimes differ from their actual meaning, based upon the context. In this post I would like to share my understanding of these terms. Entity An entity is the tabular representation of your domain class/object in the database and has an identity. In fact, an entity represents a single instance of your domain object saved into the database as a record.
Every single programming language has got its own syntax or structure; it’s own flavor and that’s what makes it standout. Go is no different. It’s easy and elegant in its own way, making to it fun to play with. In this article we will be talking about: Go program structure running a Go program comments in Go what about semicolons? revisiting the code Go Program Structure To understand the Go program structure, we need to have a Go program first.
A few days ago I came across a situation where we wanted to execute our CI pipeline locally. This article details the steps to run GitHub actions locally using nektos/act and Docker-in-Docker(dind). Why even bother? While running your CI pipeline may not seem so essential, it is definitely helpful for various reasons. The two very valid reasons listed by nektos/act are: Fast Feedback: Rather than having to commit/push every time you want to test out the changes you are making to your .
Build and Deploy an ASP .Net Core Web Application as Docker Container using Microsoft Azure – Part 3
This is the final part of the series about building an ASP .Net Core Web Application and deploying it as a Docker container using Microsoft Azure. Here, we are going to set up a Microsoft Azure DevOps release pipeline to automate the deployment of our application as a container on Azure Web App Service. If you have been following along, you should have: a GitHub repository with an ASP .
Build and Deploy an ASP .Net Core Web Application as Docker Container using Microsoft Azure – Part 2
This is the second article in the series. We are going to set up a Microsoft Azure DevOps build pipeline to automate the tasks we did manually in the first article of the series. Each time we push a change to the master branch, the build will be triggered to build our application, then build a Docker image and push it to Docker Hub. If you have been following along, you should have:
Build and Deploy an ASP .Net Core Web Application as Docker Container using Microsoft Azure – Part 1
Do you often ask yourself: I have built an ASP .Net Core Web Application, now what? How do I take it to next level using tools/platforms like GitHub, Docker, CI/CD and Microsoft Azure with my application? If YES!! You are at the right place! Introduction This article is the first in the series where we are going to: - build a simple ASP .Net Core web application - containerize it with Docker and run it on local host - push everything to GitHub for later use
This is the very first article on this blog about Docker. And I can’t tell you how excited I’m to write it. This is the very beginning of a whole new journey. Alright then, let’s get started. In this article we will be talking about: What is a Registry? Running our first Private Registry Interacting with Registry Pushing an image Pulling the new image What is a Registry?
The relationship between objects defines how these objects will interact or collaborate to perform an operation in an application. In any application, objects of user interface classes interact with the business layer objects in order to perform an operation. And in the background, the business layer objects may interact with objects of some repository which in turn talks to some data source object or service object. Case Study Before we go ahead, let’s consider a Customer Order Management application that manages the orders placed by its customers for some products.
Code reusability has always been one of the major concerns for software developers. You do not ever want to write a similar code for two business problems. You would rather like to write the solution once and reuse it whenever and wherever required. This requirement of code reusability gave rise to the concept of creating assemblies and using them in different applications by adding a reference to the same. We will get to know more about it as we have a closer look at assemblies.