.NET development
.NET backend, C# and Web API development
The backend is the part of the software users never see, yet everything else depends on it: data, business rules, security, integrations. I am Gaetano Racioppa, Software Engineer: I design and develop backend services and Web APIs in .NET and C# for companies that need to build a new system, extend one already in production or connect different applications.
I work remotely, on my own or as part of an existing team, with attention to architecture, automated tests and release procedures: the goal is code that stays reliable and maintainable over time.
The most common problems
Systems that do not communicate
ERPs, portals and apps exchanging data by hand or through periodic exports.
Fragile code
Every change risks breaking something else, because tests and a clear structure are missing.
Manual releases
Deployments done by hand, slow and error-prone, which discourage updates.
Dated technologies
Applications on unsupported versions, to be migrated gradually without stopping operations.
Backend and Web APIs
- Design and development of Web APIs and services in ASP.NET Core
- Data modelling and access to SQL Server, MySQL or MongoDB
- Authentication and authorisation of users and connected systems
- Integration with third-party systems and applications already in production
- Unit and integration tests
- CI/CD pipelines for automated build, test and release
Windows desktop applications in C#
Desktop development has different needs from backend development: installation and updates on workstations, offline use, communication with peripherals and devices. When a Windows application is needed I design it as such, without forcing the approach of a web service onto it.
Technologies and how I choose them
.NET and C# suit systems that must last: strong typing, mature testing tools, long-term support and good integration with SQL Server and Azure. I choose the database according to the data: relational when consistency and reporting matter, document-based when the structure changes often.
For code and releases I use Git, GitHub and Azure, with pipelines that run the tests on every change.
Experience
I have developed and maintained enterprise applications based on .NET, also remotely and within distributed teams, working on both the code and the release processes. Project details are confidential: I can describe their context and technical choices during a call.
“Gaetano ha svolto un ruolo cruciale nello sviluppo e nella manutenzione di applicazioni enterprise basate su .NET, dimostrando una profonda conoscenza del framework .NET e una notevole padronanza del linguaggio di programmazione C#. Le sue capacità tecniche sono accompagnate da una solida comprensione delle pratiche DevOps, che ha utilizzato per migliorare i processi di deployment e ottimizzare le performance delle applicazioni.”
How I work
- 01
First conversation
A call to understand goals, users, constraints and what already exists.
- 02
Estimate and scope
We define features and priorities together; the estimate is based on the agreed scope.
- 03
Iterative development
Intermediate, verifiable releases, so you can see and try the product as it takes shape.
- 04
Testing and quality
Automated tests and checks on real devices and environments before every release.
- 05
Release
Store publication or go-live, following a repeatable procedure.
- 06
Maintenance and evolution
Fixes, updates and new features after the first release.
Frequently asked questions
Do you build integrations with systems already in production?
Yes. I start by analysing what the system exposes (APIs, database, files, message queues) and design the integration so that it does not interfere with operations, using separate test environments when available.
Can you work alongside an existing team?
Yes. I can join the team’s workflow (repository, code review, task management tools) for a specific project or for an agreed period.
How do you handle testing and deployment?
With unit and integration tests run automatically on every change and CI/CD pipelines that make releases repeatable. The level of automation adapts to what the company already has.
How much does a .NET backend cost and how long does it take?
It depends on the number of features, the integrations with other systems, the level of polish of the interface and what already exists. That is why I do not publish price lists: after the first conversation I prepare an estimate based on the agreed scope.
Related pages
Let’s talk about your backend
Describe the system: what already exists, what it must do and which applications it has to talk to.