Eduard Keilholz

In an Azure Container Apps cloud solution, implementing a reverse proxy serves as a crucial component for several reasons. Firstly, a reverse proxy enhances security by acting as a gateway between external clients and backend services, effectively shielding the underlying containerized applications from direct exposure to the internet. This additional layer of security helps prevent unauthorized access and potential attacks and mitigates security vulnerabilities. Secondly, a reverse proxy… Meer weergeven

In an Azure Container Apps cloud solution, implementing a reverse proxy serves as a crucial component for several reasons. Firstly, a reverse proxy enhances security by acting as a gateway between external clients and backend services, effectively shielding the underlying containerized applications from direct exposure to the internet. This additional layer of security helps prevent unauthorized access and potential attacks and mitigates security vulnerabilities. Secondly, a reverse proxy facilitates load balancing and traffic distribution across multiple container instances, optimizing resource utilization and ensuring high availability and performance. Moreover, it simplifies the management of SSL/TLS certificates, handling encryption and decryption centrally, which is essential for securing data in transit. Overall, incorporating a reverse proxy in the Azure Container Apps environment not only enhances security but also contributes to scalability, reliability, and streamlined management of containerized applications. Minder weergeven

In my previous post, I explained some basic concepts here and there. Hopefully, you now understand what a computer network looks like, and what basic concepts you should take care of to create one. With this post, I try to dive deeper into the concept of Subnets. Subnets are smaller, more manageable segments of your network. There are more strategies that you can use to organize your network (with subnets). For example, you can have subnets per service, department, or application tier. Although… Meer weergeven

In my previous post, I explained some basic concepts here and there. Hopefully, you now understand what a computer network looks like, and what basic concepts you should take care of to create one. With this post, I try to dive deeper into the concept of Subnets. Subnets are smaller, more manageable segments of your network. There are more strategies that you can use to organize your network (with subnets). For example, you can have subnets per service, department, or application tier. Although choosing such a strategy is good to start with, it doesn’t take you all the way because some resources have exceptions when integrating into your Virtual Network. For example, some resources require a dedicated subnet. So the subnet is reserved for that resource only. Other resources demand a certain name for your subnet, and so on. Minder weergeven

Most of us have a home network. This network allows your devices to communicate with each other. You can stream movies using your Chromecast, you can send documents to your printer, and even turn your lights on and off again. Imagine how it would be if anyone within the reach of your network could access it. Then suddenly, everyone passing by can control your lights and Chromecast. It may be an interesting experiment, but when you have your personal data stored somewhere within your network… Meer weergeven

Most of us have a home network. This network allows your devices to communicate with each other. You can stream movies using your Chromecast, you can send documents to your printer, and even turn your lights on and off again. Imagine how it would be if anyone within the reach of your network could access it. Then suddenly, everyone passing by can control your lights and Chromecast. It may be an interesting experiment, but when you have your personal data stored somewhere within your network, you probably want something in place to protect your network resources from unauthorized individuals. Minder weergeven

With this article, I hope to take it a little bit further than other blogs do. There are a lot of articles that show Infrastructure as Code, App Deployments, or build strategies using CI/CD workflows, but not too many that tie all these techniques together. This post will take you from the beginning to the end. The focus of this article is the GitHub Actions workflow and assumes that you already have basic knowledge of GitHub Actions workflows and Infrastructure as Code for Azure (Bicep).

This blog post is part one of what I expect is going to be a large series. It’s my opportunity to build stuff in the Azure Cloud while ending up with a cool online playable game. It’s a board game, played against others. The game is not even half-way finished and I don’t know when it’s going to be finished. I don’t want to spend all my spare time. In this series, I will blog about my progress, how I designed the game from an architectural perspective, and how I solved problems as a (C#)… Meer weergeven

This blog post is part one of what I expect is going to be a large series. It’s my opportunity to build stuff in the Azure Cloud while ending up with a cool online playable game. It’s a board game, played against others. The game is not even half-way finished and I don’t know when it’s going to be finished. I don’t want to spend all my spare time. In this series, I will blog about my progress, how I designed the game from an architectural perspective, and how I solved problems as a (C#) developer. Minder weergeven

The migration of software to the cloud has begun, a long time ago… In fact, when I started writing software for the cloud somewhere in 2010, I expected us to be a lot further by now. Now, ten years later, cloud services are very mature, fairly cheap compared to on-premises hosting, and very secure. All this, makes me ask why some companies still don’t embrace the cloud. One example is scaling. It’s almost impossible to host a service on-premises and make it scale as it could in the cloud… Meer weergeven

The migration of software to the cloud has begun, a long time ago… In fact, when I started writing software for the cloud somewhere in 2010, I expected us to be a lot further by now. Now, ten years later, cloud services are very mature, fairly cheap compared to on-premises hosting, and very secure. All this, makes me ask why some companies still don’t embrace the cloud. One example is scaling. It’s almost impossible to host a service on-premises and make it scale as it could in the cloud. Distributed systems leverage this power which makes it almost too easy to build software systems that scale extremely well. But every huge advantage comes with a downside. In this story about eventual consistency, I will show how how to tackle this problem using the Azure Service Bus. Minder weergeven

Obviously, the Sec stands for Secure (or Security if you like), which means, that we’re trying to use the DevOps mechanism as secure as possible. When developing, all your systems are tied together using secrets. If you like to communicate with a SQL Database, you need a password to connect. A password that you don’t like to be spread throughout the entire internet I guess. So that password is a secret. You know the secret, maybe some others may know it or can access it, but it’s not public… Meer weergeven

Obviously, the Sec stands for Secure (or Security if you like), which means, that we’re trying to use the DevOps mechanism as secure as possible. When developing, all your systems are tied together using secrets. If you like to communicate with a SQL Database, you need a password to connect. A password that you don’t like to be spread throughout the entire internet I guess. So that password is a secret. You know the secret, maybe some others may know it or can access it, but it’s not public, and you like to keep it that way. Minder weergeven

The basics of caching is that you use a key-value to store data, and then use that same key to retrieve the same data. Values remain in the cache for a (configurable) amount of time. Once your value is gone, it’s… yeah… gone… You as a developer are also able to invalidate a value in the cache. The advantage of caching stuff is that the cached data can be retrieved super fast. So if you (for example) have a relational SQL Server database, and you just materialized some data for a certain view… Meer weergeven

The basics of caching is that you use a key-value to store data, and then use that same key to retrieve the same data. Values remain in the cache for a (configurable) amount of time. Once your value is gone, it’s… yeah… gone… You as a developer are also able to invalidate a value in the cache. The advantage of caching stuff is that the cached data can be retrieved super fast. So if you (for example) have a relational SQL Server database, and you just materialized some data for a certain view and you know this data is going to be re-used in the near future, you’re probably want to store this data in a cache mechanism to prevent you from having to query the database again with that super fancy SQL statement with over a hundred joins. Minder weergeven

I’ve been developing software for ages. I’m a backend developer writing mostly C# and yes I like cloud environments and the point where these two meet. Having that said, I need to say that I’m also very charmed by Angular and I like to experiment with it. I have experience with the latest ‘family’ of Angular versions 2 up to version 9 and a little which is the latest version at the time of writing this post. I’ve been involved with a couple of projects running some sort of a backend system… Meer weergeven

I’ve been developing software for ages. I’m a backend developer writing mostly C# and yes I like cloud environments and the point where these two meet. Having that said, I need to say that I’m also very charmed by Angular and I like to experiment with it. I have experience with the latest ‘family’ of Angular versions 2 up to version 9 and a little which is the latest version at the time of writing this post. I’ve been involved with a couple of projects running some sort of a backend system (API), consumed by an Angular front-end solution. Minder weergeven

One of my colleagues replied in a tweet by a Dutch telecom provider. They tweeted the app was down for a while because they’re updating the thing. It’s 2020 now. Downtime is a thing from the past. The Microsoft Azure cloud and Microsoft DevOps allow you to create premium high performant apps and deliver services that allow you to maintain that app with minimal downtime. While your app is growing, so is it’s technical architecture. This means that you’re not done with automagically deploying… Meer weergeven

One of my colleagues replied in a tweet by a Dutch telecom provider. They tweeted the app was down for a while because they’re updating the thing. It’s 2020 now. Downtime is a thing from the past. The Microsoft Azure cloud and Microsoft DevOps allow you to create premium high performant apps and deliver services that allow you to maintain that app with minimal downtime. While your app is growing, so is it’s technical architecture. This means that you’re not done with automagically deploying your stuff to the cloud. You must also maintain that cloud architecture. Azure provides ARM templates as a tool to do just that. Minder weergeven

At 4DotNet, we have an annual developer day. This means, that one day in a year, we all come together to challenge ourselves with one of the latest technologies/features. As we were looking for a good challenge, I remember a demo project by Microsoft that describes a game in which players get an instruction to take a picture of ‘object’. The object here changes all the time. Players can now grab their mobile device and take a picture of that object. The first player who does so wins the round… Meer weergeven

At 4DotNet, we have an annual developer day. This means, that one day in a year, we all come together to challenge ourselves with one of the latest technologies/features. As we were looking for a good challenge, I remember a demo project by Microsoft that describes a game in which players get an instruction to take a picture of ‘object’. The object here changes all the time. Players can now grab their mobile device and take a picture of that object. The first player who does so wins the round and then a new instruction with a different object will be sent out. The technique behind this game (validate if the picture taken contains the instructed object) is Azure Cognitive Services (ACS). Because I never ran into a project that uses ACS, I thought this would be a nice case for our developer day and so I proposed to re-create this game in several teams during our developer day. Then our CEO came in and said that it would be fun to create the game, but isn't challenging enough because it “can't be that hard to call an API in Azure”. I Agreed on him, but since I (again) never used ACS, I was still curious about the system and so I started just a small project to see how it works. So here we go… Minder weergeven

I have a Canon 700D photo camera, which I’m very happy with. For my previous camera I bought a (wired) remote control. Just plug the wire in and and press the button on the remote if you want to make a picture. Lately I decided to try to take this a step further and automate the button press. Ultimately add a timer process to make the automated picture repeat over a certain amount of time.

Storing Images in SQL Server using EF and ASP.NET

Probably the fastest XML Reader application for large XML files

How do you programmatically size images properly