The best technology is the one that won’t get in the way tomorrow.
We decide not by trend, but by depth of work, data, operations and the next realistic expansion.
Not everything has to be on the web. Not everything should remain on the desktop.
Deep work stays native.
Large volumes of data, keyboard-driven speed, device access and complex forms deserve a robust desktop.
Access becomes web-based.
Self-service, approvals and external roles belong where they are accessible without installation.
The rules remain shared.
A domain core prevents the client, portal and API from developing three different truths.
You don’t need to order a stack.
Describe the work. We find the technology that serves it unobtrusively.
Frequently asked questions about technology and architecture
Technological decisions must fit the team, the domain and operations. That is why we don’t resolve these questions abstractly, but always with the concrete system in mind.
When is Delphi sensible compared to a complete new platform?
Whenever established domain logic, high-performance desktop processes and multiplatform goals should be carried forward economically, instead of recklessly replacing existing substance.
When do you use C# in addition?
Primarily for portals, web backends, REST services, integrations and service-oriented architecture parts that integrate well with existing desktop systems.
How important is Layer-3 in practice?
Very. Only a clean separation of UI, business logic and data access makes modernization, testing, services and future platform changes manageable.
Do you consider new platforms like Windows 11 ARM64 early on?
Yes. New target hardware and deployment paths are tested early so they don’t later become costly special projects.
Read further questions in one place
These short answers remain here on the page. On the central FAQ landing page we contextualize the topic further in relation to architecture, modernization, platforms and operations.
Next step
If you have a concrete modernization, API or platform question, we should establish the technical scope clearly and early.
Net-Base evaluates existing systems, data paths, interfaces and target platforms not in isolation, but in the context of domain logic, operations and future expansion.
- Current state, target state and technical risks are assessed jointly.
- REST, data access, portals and rollout are not deferred to a later stage as secondary consequences.
- You can see early on which path is economically and operationally viable.