Belitsoft > .NET Case Studies Examples

.NET Case Studies Examples

According to Belitsoft, .NET remains a mainstream enterprise backend platform in the U.S. software market in 2026

Portfolio

Software Project Rescue: All Websites Back Up and Running, Business Saved (2026)
Software Project Rescue: All Websites Back Up and Running, Business Saved (2026)
The client’s websites were down almost all the time. The previous provider did a bad job. The client hired Belitsoft to take over the web application and make it stable. Belitsoft’s DevOps engineers and developers rescued the cloud server and the web application and got all the client’s web services back online. Today, this network of websites is running properly, and the client has stopped worrying and is comfortable sleeping at night.
Custom Investment Management and Copy Trading Software with a CRM for a Broker Company
Custom Investment Management Software for a Broker Company
For our client, we developed a custom financial platform whose unique technical features were highly rated by analysts at Investing.co.uk, compared to other forex brokers.
Mixed-Tenant Architecture for SaaS ERP to Guarantee Security & Autonomy for 200+ B2B Clients
SaaS ERP Mixed-Tenant Architecture for 200+ B2B Clients
A Canadian startup helps car service bodyshops make their automotive businesses more effective and improve customer service through digital transformation. For that, Belitsoft built brand-new software to automate and securely manage daily workflows.
15+ Senior Developers to scale B2B BI Software for the Company Gained $100M Investment
Senior Developers to scale BI Software
Belitsoft is providing staff augmentation service for the Independent Software Vendor and has built a team of 16 highly skilled professionals, including .NET developers, QA automation, and manual software testing engineers.
Mobile App for a Delivery Marketplace
Mobile App for a Delivery Marketplace
Our client, a European medium-sized logistics provider, came to Belitsoft with a long-term strategy for entering the same-day delivery market with the help of a mobile app.
Migration from .NET Framework to .NET Core and AngularJS to Angular for HealthTech Company
Migration from .NET Framework to .NET Core and AngularJS to Angular for HealthTech Company
Belitsoft migrated EHR software to .NET for the US-based Healthcare Technology Company with 150+ employees.

Recommended posts

Belitsoft Blog for Entrepreneurs
Inside JPMorganChase' Fintech .NET Product Engineering
Inside JPMorganChase' Fintech .NET Product Engineering
Why .NET Is JPMorganChase's Choice for Enterprise Product Engineering  JPMorganChase is one of the oldest American financial institutions, with more than 200 years of history. In 2026, senior .NET developers help JPMorganChase's Commercial & Investment Bank teams in Irvine (CA), Plano (TX) and Chicago (IL) design and deliver software products for healthcare payments (electronic payment processing through InstaMed platform), securities services (custody and fund administration for institutional clients), and electronic trading (multi-broker trading through Neovest platform). Modern .NET fits JPMorganChase's product engineering strategy because as a cloud-native strategy it requires containerization, orchestration, resilience, security, observability, and CI/CD — every one of which .NET supports natively.  .NET Supports Cloud-Native Containerization JPMorganChase has built one of the largest container-based infrastructures in banking. The bank packages its software into standardized containers or portable units that include the software and everything it needs to run, ready to deploy anywhere from the bank's own data centers to public clouds. JPMorganChase uses .NET inside this container-based infrastructure for healthcare payments, securities custody, fund administration, and electronic trading.  Cloud-native containerization is important to JPMorganChase because the bank's size (tens of thousands of engineers building thousands of services) requires portability across the bank's hybrid infrastructure, standard packaging across different development teams, and efficient use of server capacity. Without containerization, it would be significantly harder for a bank of this size to deploy across multiple clouds, keep development teams working the same way, and control server costs at this scale.  Containers let the bank run the same applications on AWS, Azure, Google Cloud, or its own data centers without dependency on one cloud vendor.  They give every development team the same way to package software.  And by allowing more services to run on each server, containerization can reduce the costs of hosting them. .NET Capabilities for Cloud-Native Containerization Built-in Container Packaging If each team at banks or other large organizations writes its own instructions (Dockerfiles) for packaging software into containers, different instructions will produce inconsistent results and security gaps. .NET packages software into containers, using Microsoft's official building blocks by default, without requiring a separate Dockerfile. So the bank's software delivery processes have one less tool to maintain and one less place where security mistakes can happen.  Official Microsoft Container Images .NET fits the supply-chain documentation aspect of containerization. Container images are software components. When banks use them, they come under the same third-party software risk management scrutiny as everything else the bank uses: what is in them, who maintains them, how quickly security flaws get fixed. Microsoft provides official .NET base images that banks use as the foundation for their production application images, signed and patched as Microsoft products. So the bank can show Microsoft's documentation instead of writing its own.  Stripped-down Container Packages (Chiseled Images) The bank runs hundreds of services in containers, and every piece of software inside every container is a potential security vulnerability the security team has to track and fix. Microsoft provides a special version of their Linux-based container packages for .NET that includes only what the software needs to run and nothing else. So the bank's .NET services run on the smallest possible foundation, with the smallest target for attackers and the shortest list of security fixes the security team has to apply.  AOT Compilation The orchestrator inside cloud-native containerization infrastructure scales software up and down based on demand, but a container that takes too long to start cannot scale up fast enough to handle traffic spikes. Moreover, large software packages cost more to store and distribute across the bank's servers. .NET has a way to prepare software in advance, before it runs, producing containers 80-90% smaller than before and starting in milliseconds. This reduces the bank's infrastructure cost for every service it operates. Container-Aware Runtime Cloud-native containerization gives each piece of containerized software a strict budget for how much computer memory and processing power it can use. If the software uses more than its budget, the system shuts it down and starts a fresh copy, which causes banking transactions in progress to fail. Container-aware runtime lets .NET software automatically adjust to the resource budget (memory, processing power) it has been given inside a container. So .NET-built software does not exceed its limits, does not get shut down, and the bank does not lose transactions. .NET Fits Cloud-Native Orchestration  JPMorganChase manages its containerized software through Kubernetes, the platform that keeps the bank's services running by starting new copies when load increases, replacing failed copies automatically, and sending customer requests only to working services. A dedicated engineering team at the bank builds and operates Kubernetes across the bank's hybrid infrastructure, including Amazon's EKS on AWS plus Kubernetes on Azure, Google Cloud, and the bank's own data centers. JPMorganChase's .NET workloads in healthcare payments, securities custody, fund administration, and electronic trading all operate under this Kubernetes management. Cloud-native orchestration is important to JPMorganChase because the bank's services run 24/7 across global business lines and cannot wait for an engineer to restart them when they fail. Without orchestration, it would be significantly harder for a bank of this size to keep services running through failures, traffic spikes, and software updates.  The orchestrator automatically restarts failing services and routes customer requests away from them.  It scales services up and down as banking workloads change throughout the day.  And it lets the bank deploy software updates without taking services offline.  .NET Capabilities for Cloud-Native Orchestration  Built-in Health Check Endpoints Kubernetes needs to know which copies of a service are healthy enough to receive customer requests and which need to be restarted. Without feedback from each service, Kubernetes does not know which copies are available and which are down. It keeps sending customer requests to all copies, including broken ones, and customers see errors. .NET has built-in health check endpoints for Kubernetes. So Kubernetes restarts failing .NET services automatically and sends customer requests only to .NET services that are working. Built-in Key Management for Scaling When traffic increases, Kubernetes starts more copies of a service to share the load. But running multiple copies of the same service creates a problem: how do customer logins, encrypted cookies, and security tokens work across copies? .NET has built-in key management for multi-copy situations, sharing the necessary security keys across all running copies of a service automatically. So the bank's .NET services scale up without logging customers out or breaking their security tokens when Kubernetes starts new copies. Graceful Shutdown If Kubernetes is going to shut down a copy of a service due to a software update, scaling down, or server maintenance, it tells the service to finish its current work and then shut down. If the service does not understand this request and keeps working, Kubernetes stops it forcibly, which may interrupt the banking transactions the service was processing and cause them to fail. .NET understands the request from Kubernetes and finishes the transactions it is currently processing before shutting down. So when JPMorgan Chase updates its .NET services or scales them down, customers in the middle of paying a bill, placing a trade, or accessing their accounts can complete their actions instead of seeing errors. .NET Has All Tools Required to Implement Cloud-Native Resilience Patterns If orchestration is about managing failures at the infrastructure level by restarting failed copies of a service and redirecting customer requests away from broken ones, resilience covers failures inside the bank's software itself, when one piece of it needs an answer from another one but the answer is slow or never comes. JPMorganChase requires application resiliency from the code in the bank's software to keep it working, even when other systems it needs answers from, like an account service, a fraud check, or a customer database, slow down or fail. JPMorganChase's senior .NET engineers apply these resiliency practices when building software for healthcare payments, securities custody, fund administration, and electronic trading. Cloud-native resilience is important to JPMorganChase because the bank's software needs answers from many other systems to process a single customer transaction, and a slow or failing system would otherwise stop the transaction from completing. Without resilience patterns, it would be significantly harder for a bank of this size to keep customer transactions moving through temporary problems, avoid leaving customers waiting forever when a problem cannot be solved, and keep the rest of the bank's software working when one part fails. When a request doesn't go through because of a short outage, the retry pattern forces the code to wait a moment and try again, up to a set number of attempts. For example, when a patient's insurance payer briefly doesn't respond to an eligibility check from a doctor's office, JPMorganChase's InstaMed payment technology, working under this pattern, can keep retrying ahead of the visit until the payer starts responding, so the patient checks in and the visit goes ahead without the staff or the patient noticing anything went wrong. However, if the response from a service is taking too long, the timeout pattern forces the code to stop waiting. Any wait that takes too long often makes software unresponsive, causing irritation. So, for example, when one broker is slow to acknowledge an order on JPMorganChase's Neovest platform, the timeout cuts off the wait, and the trader can route the order to a different broker instead. Without isolation, a slow part of a system can make other parts of it also slow, so another pattern, the bulkhead pattern, forces the code to isolate the work with this slow part from other parts. So, for example, when JPMorganChase's fraud-monitoring system slows down, customers can still log in to the Chase Mobile app, see their balances, and view their recent transactions. .NET Capabilities for Cloud-Native Resilience Microsoft actively promotes cloud-native reliability. Its Azure Well-Architected Framework documents 31 design patterns that support reliable software, and many of them are, in essence, resilience patterns. Microsoft also develops its own products with these patterns in mind, so .NET 10 is no exception. For cloud-native systems where one piece of software depends on many others, like JPMorganChase's banking software, five core resilience patterns - retry, timeout, circuit breaker, bulkhead, and fallback - have high priority and are strong requirements for any .NET engineer working in a bank. .NET 10 has built-in tools to implement all of these core patterns. Built-in Outbound Resilience Pipeline Modern banking software platforms often use microservices: separate services for business capabilities such as accounts, payments, customer data, pricing, or ledger functions. Banking microservices exchange requests, responses, events, and data via HTTP/REST as a major synchronous method. No one can guarantee that when one banking microservice asks a second microservice for information (for example, to service a bank client's request), the answer comes back right away. So the question is what a microservice should do when it doesn't get a response. Senior architects use a special configuration mechanism that manages microservice behavior in these situations. A good development platform has to include such a configuration mechanism, otherwise there is no uniformity in how different microservices work, and every microservice team will configure microservice behavior its own way. Enterprise doesn't tolerate that kind of architectural mistake, especially in banking. Microsoft accounts for this modern requirement and offers a solution in its .NET platform: the Microsoft.Extensions.Http.Resilience component. It is responsible for the logic of how a microservice works when it doesn't get a response from another microservice: retry, circuit breaker, and timeout. For example, it determines whether the problem was temporary, and if so, whether it resolves after a short period of time. If it resolves quickly, work continues so the bank client doesn't even notice. If it doesn't resolve quickly, the bank client doesn't wait forever for a solution and instead gets an answer that the service is currently down. And at the internal level, the unresolved request isn't allowed to pull all the cloud resources onto itself, which would otherwise hang the whole system. Built-in Graceful Degradation with Cached Data If a bank app customer is trying to do some operation, do not show an error right away, even if technically there is one. Resilience engineers insist on that. One elegant technical solution used in the industry is to show data from cache when fresh data is temporarily unavailable. The cached data may already be stale. But stale data with a timestamp is often better than no data and a dead screen. For example, instead of showing "balance data unavailable because the service did not respond", the app can show "balance as of 9:22". Even if it is already 12 PM, and the balance may have changed, the customer still sees something useful. Any resilience strategy needs to be centralized for the reasons already discussed, and pulling data from cache is no exception. The Microsoft.Extensions.Http.Resilience component mentioned earlier lets you implement this kind of fallback from one place too. The bank avoids empty screens and unnecessary "service unavailable" responses when slightly stale data is still useful.
Inside Citi's Banking .NET Modernization and Process Automation
Inside Citi's Banking .NET Modernization and Process Automation
Why Does Citi Stick With .NET During Modernization and Process Automation? Citi is one of the oldest and largest banks in the world. In 2026, .NET developers help Citi's Enterprise Operations & Technology team in Jacksonville and Tampa, Florida, revise its legacy financial platforms while reimagining client and partner experiences. Modern .NET fits this top US bank's modernization strategy because the modernization strategy is based on several pillars that .NET supports, including distributed microservices, hybrid data workflows, and cloud-native containers and orchestrators. .NET Fits Distributed Microservices Architecture Citi is modernizing older application systems. They are engineering these services in .NET, using a microservices architecture and proven design patterns, which lets different components of their financial applications be developed, deployed, and scaled independently. .NET developers at Citi also create RESTful APIs in .NET. These APIs are required so other applications, departments, and/or external partners can request and receive data from Citi's databases, such as MS SQL, Oracle, or Couchbase. Citi developers also write .NET code that calls the APIs of other systems within the bank to get the data their target applications need to function. Citi is also upgrading its .NET architecture with Kafka. Typically, microservices make a data request through an API, thereby waiting for a response. With Kafka, this synchronous wait is removed, as services can publish real-time financial data and continue to operate while other services read the data whenever they choose. This makes the system more independent and faster. .NET Works Well With Cloud-Native Containers and Orchestrators To support a microservices architecture, the underlying infrastructure of Citi is also shifting to containers and orchestration platforms. Citi's .NET developers package microservices built with .NET into portable containers using Docker and run them on OpenShift, a Kubernetes-based orchestration platform, where containers are managed automatically at scale to guarantee reliability and fast, uniform deployment cycles. .NET Supports Fast CI/CD With Traceable, Compliant Releases Citi deploys its financial applications, based on .NET Core microservices and backend services, through Lightspeed, its internal CI/CD platform built on Tekton and Harness DevOps tools, with GitHub for source control. A commit or merge to GitHub triggers the deployment pipeline. Tekton, a CI/CD engine running on Kubernetes, builds and tests the service and produces a container image. Harness, a deployment and release-orchestration platform, then promotes and releases that image safely. .NET fits this CI/CD pipeline ideally: its standard SDK builds, tests, and packages the code through one toolchain, so each change moves through this deployment pipeline quickly. What else .NET contributes to Citi's CI/CD:  .NET builds are reproducible, so what gets deployed is exactly what was tested. Each .NET build is uniquely identifiable, so any release traces back to a build with a specific version number. .NET tests produce a clear pass/fail result, which the pipeline's gate uses to stop a bad release before production, lowering the probability of incorrect transactions or downtime for mission-critical financial applications. Automated CI/CD lets Citi release to its .NET financial systems fast, repeatedly, and safely, every change traceable, every release tested before it deploys, the control a bank is required to maintain.  .NET Suits Apps That Need Both Relational and NoSQL Databases Citi is modernizing its databases too, using both relational and NoSQL platforms with .NET as the engine connecting them.  There is a lot of financial data and it comes in different forms and one type of database simply cannot cover them all, that's why Citi pairs MS SQL and Oracle with Couchbase. Relational databases manage structured, transactional financial data, while NoSQL platforms are designed for high-performance, flexible storage well-suited to modern web interfaces that must be responsive even if they process large volumes of unstructured data for many users.  For this hybrid store, .NET developers first build scalable schemas, stored procedures and functions on both database types. They then add backends, automated workflows, and microservices in C# that connect the frontend UIs to this store. The result combines SQL's transactional integrity with NoSQL's flexibility behind a single .NET application.  .NET APIs Give Angular Frontends Fast and Secure Data As part of building new and revised application systems, full-stack .NET engineers develop client-facing web interfaces using Angular for Citi's banking applications. Angular sends requests to ASP.NET Core APIs to get dynamic data and update the UI as needed, while the ASP.NET Core backend manages logic, authentication, and database access on the server to keep them secure. ASP.NET Core is a high-performance framework that processes these requests with low latency, so Angular interfaces stay fast and responsive for users. .NET Has Capabilities That Banking Workflow Automation Needs Citi is modernizing its application systems, building new and revised systems and streamlining processes, and automation is a central part of that work. Cross-system automation is especially important for high-volume processes in a regulated financial environment, such as fraud detection, prevention, and investigation.  .NET developers automate end-to-end business processes through custom .NET and C# software, microservices, backend services, and scheduled or triggered processes.  Banking workflow automation needs the code to do specific things, and .NET has the matching capability for each: Call REST APIs reliably Read and write multiple database types Manage concurrency at production volume Execute scheduled and triggered jobs Produce audit trails and logging Operate inside the container and CI/CD stack Citi already uses Interact with application UIs where needed .NET, primarily through C#, ties APIs, databases, and UIs together, so the whole automated workflow can be written and maintained as .NET code. How .NET Developers from Belitsoft Can Help with Banking Software Development

Our Clients' Feedback

Any software development, programming, or design needs we have had, Belitsoft company has always been able to handle this for us

We have been working for over 10 years and they have become our long-term technology partner. Any software development, programming, or design needs we have had, Belitsoft company has always been able to handle this for us.

We are very happy with Belitsoft

Belitsoft has been the driving force behind several of our software development projects within the last few years. This company demonstrates high professionalism in their work approach. They have continuously proved to be ready to go the extra mile. We are very happy with Belitsoft, and in a position to strongly recommend them for software development and support as a most reliable and fully transparent partner focused on long term business relationships.

We can recommend Belitsoft and are looking forward to start a follow-up project

It was a great pleasure working with Belitsoft. Software Development Company. New requirements and adjustments were implemented fast and precisely. We can recommend Belitsoft and are looking forward to start a follow-up project.

We are definitely looking at Belitsoft as a long-term partner

They use their knowledge and skills to program the product, and then completed a series of quality assurance tests. We were working in an agile way with them. Belitsoft performed very well throughout our project. We are definitely looking at Belitsoft as a long-term partner.

I highly recommend Belitsoft for website design and development

I highly recommend Belitsoft for website design and development. We were up against a tight deadline to launch the project. The work was delivered on time and within budget! I will continue working with Belitsoft as a valued partner for our web development!

We would recommend them to anyone who is in need of custom programming work

We have worked with Belitsoft team over the past few years on projects involving much customized programming work. They are knowledgeable and are able to complete tasks on schedule, meeting our technical requirements. We would recommend them to anyone who is in need of custom programming work.

Belitsoft seems to know what they're doing, which I appreciate

Belitsoft company is able to make changes instantly. One of our internal engineers has commented about how clean their code is. Belitsoft seems to know what they're doing, which I appreciate.

We continue today to augment our existing staff with great developers from Belitsoft

Belitsoft company has been able to provide senior developers with the skills to support back end, native mobile and web applications. We continue today to augment our existing staff with great developers from Belitsoft.

We highly recommend that you use this company if you want the same benefits

Belitsoft company delivered dedicated development team for our products and technical specialists for our clients time to time custom development needs. We highly recommend that you use this company if you want the same benefits.

They were able to convert it into a multi-platform software solution

We approached BelITsoft with a concept, and they were able to convert it into a multi-platform software solution. Their team members are skilled, agile and attached to their work, all of which paid dividends as our software grew in complexity.

Belitsoft guarantees first-class service through efficient management, great expertise, and a systematic approach to business

Having worked with Belitsoft as a service provider, I must say that I'm very pleased with the company's policy. Belitsoft guarantees first-class service through efficient management, great expertise, and a systematic approach to business. I would strongly recommend Belitsoft's services to anyone wanting to get the right IT products in the right place at the right time.

If you are looking for a true partnership Belitsoft company might be the best choice for you

If you are looking for a true partnership Belitsoft company might be the best choice for you. They have proven to be most reliable, polite and professional. The team managed to adapt to changing requirements and to provide me with best solutions. I strongly recommend Belisoft.

I expected and demanded a lot of you at Belitsoft company, but you exceeded my expectations

I expected and demanded a lot of you at Belitsoft company, but you exceeded my expectations. You acted pro-actively, challenged me at the right moments. Thanks!

Let's Talk Business
Do you have a software development project to implement? We have people to work on it. We will be glad to answer all your questions as well as estimate any project of yours. Use the form below to describe the project and we will get in touch with you within 1 business day.
Contact form
We will process your personal data as described in the privacy notice
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply
Contact us

USA +1 (917) 410-57-57
700 N Fairfax St Ste 614, Alexandria, VA, 22314 - 2040, United States

UK +44 (20) 3318-18-53
26/28 Hammersmith Grove, London W6 7HA

Poland +48 222 922 436
Warsaw, Poland, st. Elektoralna 13/103

Email us

[email protected]