Start a project

Why we build on .NET, Blazor and Azure

The reasons our agency builds client platforms on .NET, Blazor and Microsoft Azure, where the stack fits well, and where we would pick something else.

Clients rarely ask which programming language we use, and they should not have to care. But the choice of technology decides things they do care about: how long the system will last, how many people can maintain it, what it costs to run, and how safe it is. This is an explanation of our choice, written for the person who signs the contract as much as for the one who reads the code.

One language from the database to the screen

Most web systems are written in at least two languages. One runs on the server, and JavaScript runs in the browser. Each side has its own tools, its own libraries and often its own developers. The rules of the business, such as how a price is calculated or what makes an order valid, end up written twice, and the two copies drift apart.

With .NET, we write C# on the server. With Blazor, we write C# for the browser too. A rule is written once and shared. The developer who builds the screen can read and fix the code behind it. For a client this means fewer handovers between specialists, fewer bugs caused by two versions of the same logic, and a smaller team that understands the whole system.

What Blazor gives a business

Blazor is Microsoft's framework for building web interfaces with .NET. It suits the kind of software we build most: portals, back-office systems, dashboards and platforms where people log in and work for hours.

  • Pages can be rendered on the server, so they load quickly and search engines can read them.
  • Parts of a page can be made interactive where interactivity is needed, without turning the whole site into a heavy application.
  • Interfaces are built from components that are reused across the system, which keeps screens consistent.
  • The same components can be placed inside a mobile or desktop app, which we cover in a separate article on .NET MAUI.
One language and one set of tools, from the database to the screen.
One language and one set of tools, from the database to the screen.

Why Azure

We host on Microsoft Azure because it fits the stack and because it removes work that should not be done by hand. Deployment is automated. A new version can be started beside the old one and swapped in once it is healthy. Secrets such as keys and connection strings are kept in a vault and not in files. Databases are backed up by the platform.

Identity is the other reason. Microsoft Entra handles sign-in, including the company accounts that many of our clients' staff already use for email. We would much sooner rely on that than write our own password storage. For data we use SQL where the information is relational and Cosmos DB where it needs to scale across documents and regions. In front of it all we put Cloudflare for caching and protection.

Azure has data centre regions in many parts of the world, including Europe, the United States and the Gulf, so a system can run close to its users. If your sector has rules about where data lives, confirm them with your regulator or adviser first.

Long support and a large talent pool

A business system should be expected to run for many years. .NET is open source, runs on Windows and Linux, and is released on a published schedule with long-term support versions. Upgrades from one version to the next are usually modest pieces of work, not rewrites.

A widely taught language means your next developer is easy to find.
A widely taught language means your next developer is easy to find.

C# is also widely taught and widely used, in Lebanon, in the Gulf and in the United States. That matters to you on the day you want a second opinion, an internal hire or a different agency. You will find people who can read the code.

We also give back to this ecosystem. Angry Monkey Cloud is our set of free .NET developer libraries, and Coconut Sharp is our .NET hosting platform.

Where this stack is not the answer

We do not use it for everything. A content site that a marketing team wants to edit daily, with a familiar editor and a wide choice of plugins, is often better served by WordPress. An e-learning programme is usually better on Moodle, which already does what schools and training departments need. We work with both when the project calls for it.

If a client already has a capable in-house team on another stack, we will say so and not push them to change. The right technology is the one that fits the work and the people who will maintain it.

How Angry Monkey Agency can help

Angry Monkey Agency has been building on Microsoft technology for nearly ten years, for clients in Lebanon, the GCC, Africa and the USA. If you are planning a platform, or you have a .NET system that needs a team to look after it, we would be glad to look at it with you.

The same team has worked on campaigns and digital work for brands such as stc, American Express, Burger King and Nissan. Read how we work in software development, look at the work or start a project.

Chat with us on WhatsApp