Modernize a legacy Delphi system to AWS in Manaus
By Kevin Marcondes · Published on · Updated on · 6 min read
Moving a legacy Delphi system to AWS for companies in Manaus reduces the risks of on-premises servers, adds elasticity and enables modern integrations. Migration can be done incrementally, combining rehost, replatform and refactor based on desired impact. This page outlines signs that migration is needed, strategies, a reference architecture and a practical roadmap to decide the next steps safely.
When it makes sense to move your Delphi system to the cloud
Delphi client-server applications can still deliver value but often block further evolution. Moving to AWS helps when availability, security and integrations become priorities and on-premises infrastructure hinders progress.
- Failures or slowdowns during peak hours.
- Difficulty integrating APIs and new channels.
- Rising costs and risks of maintaining local servers.
- Audits requiring formal controls and backups.
- Remote teams accessing the system with instability.
Strategies: rehost, replatform and refactor
Legacy modernization typically combines three approaches. They differ in required effort and expected gains. The best practice is to start small, validate, and iterate. Below is a table to guide the decision.
| Path | When to use | Impact on Delphi code | Relative cost | Relative time |
|---|---|---|---|---|
| Rehost (lift-and-shift) | Quickly leave the local server | None or low | Low to medium | Short |
| Replatform | Adopt managed services (database, file storage) | Low to medium | Medium | Medium |
| Refactor | Expose business logic via APIs, modularize and optimize | Medium to high | Medium to high | Medium to long |
Practical steps in a migration project
A low-risk path usually follows short phases with verifiable deliveries. If you need an initial assessment, consider software consulting.
- Discovery: inventory of modules, dependencies and data. See software consulting.
- Quick wins: move backups and logs to S3 and enable monitoring.
- Pilot: rehost the app and database in test environments.
- Replatform: adopt RDS, FSx or other suitable managed services.
- Refactor: create REST APIs for critical functions.
- Controlled cutover: incremental migration of users and routines.
- Assisted operations: fine tuning and post-go-live metrics. See software maintenance.
Reference architecture on AWS for Delphi applications
For Delphi applications it's common to start with Windows EC2 for the app, RDS for the database (PostgreSQL, MySQL or SQL Server), FSx for Windows File Server for shared files, S3 for backups, a VPC with private subnets and a load balancer for exposed services.
Follow best practices: use IAM with least-privilege, enable observability with CloudWatch and review designs using the AWS Well-Architected Framework. If your environment is hybrid, a Site-to-Site VPN helps during transition. Consult the AWS site for the Well-Architected Framework.
If your operation requires extra focus on infrastructure and availability, data center management can complement the planning.
Common critical points in Delphi and how to address them
Legacy Delphi applications carry dependencies that influence the chosen strategy. Anticipating these items reduces rework and downtime.
- BDE/DBExpress: evaluate migration to FireDAC and compatibility with RDS.
- 32-bit components and DLLs: validate on a supported Windows Server.
- Legacy reports and remote printing: review spooling and drivers.
- Access to local files: move to FSx or S3 with ingestion routines.
- Monoliths: gradually expose functionality via REST APIs.
Costs, performance and latency for companies in Manaus
The São Paulo region (sa-east-1) is often the primary choice for Brazil due to proximity. Plan for latency between Manaus and that region using caching, queues and API layers. For web scenarios, use content distribution to reduce round-trip time.
Optimize costs by choosing instance sizes proportional to load, selecting the right class of managed database and applying storage lifecycle policies. When appropriate, autoscaling prevents overprovisioning.
Governance, security and continuity
Define access controls (IAM), environment segregation, encryption in transit and at rest, and backup policies with restoration tests. Plan RTO/RPO according to business risk.
After migration, maintain update routines, observability and regression tests. See software maintenance for support and enterprise software development when new features are required.
Frequently asked questions
Do I need to rewrite my entire Delphi system to move to AWS?
Not necessarily. Many projects begin by rehosting application servers in EC2 and replatforming databases to managed services, then refactoring critical modules over time by exposing APIs and reducing coupling. A full rewrite is considered only when continued maintenance of the legacy code becomes clearly more costly or risky than incremental modernization and migration.
How can I migrate the database without stopping operations?
Use replication and short cutover windows to keep systems available during migration. Tools such as AWS Database Migration Service can synchronize data between source and target while the application remains active. The exact approach depends on data volume, database engine and the business’s acceptable downtime, so run a pilot to validate replication and cutover steps.
What if my system uses very old Delphi components?
Inventory and map critical dependencies like BDE, DBExpress, old DLLs and COM components and test them on a supported Windows Server image. If components are incompatible, options include isolating affected modules, replacing or updating components, or exposing needed functionality via REST services while leaving remaining parts operational to minimize disruption.
Will latency from Manaus to São Paulo affect usability?
It depends on usage patterns: applications with many synchronous round-trips are more sensitive to latency between Manaus and São Paulo. Mitigation strategies include designing granular APIs, adding caching, using queues to decouple flows, introducing an intermediary cloud layer, and applying content distribution for web assets to reduce perceived latency and improve responsiveness.
How do I estimate AWS costs for a legacy Delphi system?
Estimate required CPU, memory, storage and network traffic from existing usage and logs, then size cloud instances and managed databases accordingly. Start with a conservative pilot, monitor real metrics, and adjust sizing and storage lifecycle policies. Managed services and autoscaling help control costs; short proofs of concept provide visibility before a full cutover.
Want to assess the feasibility of migrating your Delphi system to AWS in Manaus?
Share context, dependencies and priorities. We’ll map risks, benefits and a phased roadmap—from rehost to refactor—at a pace that fits your business.
Schedule a conversation