6.2 KiB
Replatform
Replatforming involves upgrading an application from it's existing legacy platform to a more modern cloud platform. It means replacing traditional application components (such as databases and middleware) with Open Telekom Cloud services, but without changing the core architecture of applications.
For example, you can replace relational databases with cloud database services from Open Telekom Cloud, replace self-built message middleware with message queue services provided by Open Telekom Cloud, and replace self-built cache databases with cache database services on Open Telekom Cloud. This makes management less expensive and makes applications more efficient and scalable.
Open Telekom Cloud provides the following solutions to migrate customers' self-built databases and middleware or those on third-party cloud platforms:
| Ob ject | Type | Sou rce | Target | Migration Method | Pros and Cons |
|---|---|---|---|---|---|
| Data base | SQL Se rver | S elf -bu ilt /DB aaS | OTC Cloud RDS for SQL Server | Data Replication Service (OTC Cloud) | The target is RDS, and the downtime is a few minutes. |
| M ySQL | OTC Cloud RDS for MySQL | Data Replication Service (OTC Cloud) | The target is RDS, and the downtime is a few minutes. | ||
| Po stgr eSQL | OTC Cloud RDS for PostgreSQL | Data Replication Service (OTC Cloud) | The target is RDS, and the downtime is a few minutes. | ||
| Mon goDB | OTC Cloud Document Database Service | Data Replication Service (OTC Cloud) | The target is RDS, and the downtime is a few minutes. | ||
| Mi ddle ware | R edis | S elf -bu ilt /Cl oud se rvi ces | OTC Cloud D istributed Cache Service (DCS) for Redis | DCS-Migration | The target is DCS. |
| S elf -bu ilt /Cl oud se rvi ces | OTC Cloud D istributed Cache Service for Redis | Redis-port | Offline export and import | ||
| K afka | S elf -bu ilt | OTC Cloud D istributed Message Service (DMS) for Kafka | MirrorMaker | Only data in Kafka clusters can be synchronized. Consumer groups or consumption progress cannot be synchronized. |
Consider the following typical architecture: A company uses Kafka message middleware to mask performance inconsistencies between front-and back-end applications. The applications get decoupled. They use a Redis database cache for hot data and MySQL databases for core service data. In a traditional IDC, the company needs to build their own middleware and databases, implement HA deployment, backup and restore solutions, and maintain corresponding components. Deployment can be inefficient, O&M expensive, and capacity expansion difficult.
Open Telekom Cloud provides cloud services that let companies deploy middleware and database components on the cloud. These services simplify middleware and database deployment and O&M. Companies can enjoy the following benefits:
- Instances can be provisioned in just minutes, so they can take advantages of pay-per-use middleware and database services.
- Cloud services can be deployed in HA configurations. They can deploy active and standby MySQL instances and Kafka/Redis clusters, and use cross-AZ deployment for data center-level HA.
- There is pay-per-use cloud middleware, such as message middleware and cache database, and diverse instance specifications. Easy capacity expansion is easy so they can start small and grow big
- They don't have to worry about O&M of middleware and databases, which saves money on O&M.