简体   繁体   English

将旧应用程序的用户迁移到工作应用程序上的新应用程序

[英]Migrating users of old application to new one on working application

I am thinking about possibe ways of migrating users between two systems. 我正在考虑在两个系统之间迁移用户的可能方式。 It is financial system, a web application (Java, Spring, Hibernate, Oracle, JBoss, etc). 它是金融系统,一个Web应用程序(Java,Spring,Hibernate,Oracle,JBoss等)。 There are 500k users to migrate together with their data like accounts, contractors, transfers, many others. 有50万用户与他们的数据一起迁移,例如帐户,承包商,转移,许多其他数据。 New application is already working and has 10k users. 新的应用程序已经可以使用并且拥有1万名用户。

Currently I am only thinking about online / offline migration. 目前,我只考虑在线/离线迁移。 Online means, that the applications stays accessible to its users during migration, offline means that I turn it off and display technical break message and the migrations is processing. 联机是指在迁移过程中用户仍然可以访问应用程序,而脱机是指将其关闭并显示技术性故障消息,并且正在进行迁移。 The client doesn't want to turn the application off so it would mean online migration. 客户端不想关闭应用程序,因此意味着在线迁移。 When the application is on (accessible to its users), many users may perform different operations (also using externals systems) and many background processes are working and changing database data. 当应用程序打开时(其用户可以访问),许多用户可能会执行不同的操作(也使用外部系统),并且许多后台进程正在工作并且正在更改数据库数据。 It would be quite risky to migrate online: - no database backup as during migration many users would do different things in application, so there would be no point of return, - problems during migration could block users that are online (database, transaction locks etc). 在线迁移非常危险:-没有数据库备份,因为迁移期间许多用户会在应用程序中做不同的事情,因此不会有返回点,-迁移期间的问题可能会阻止在线用户(数据库,事务锁定等) )。

And maybe you have some strong points to convince my customer that online migration is nonsense? 也许您有一些强项可以说服我的客户在线迁移是胡说八道? They propably could be divided by the application layer - the Jboss server risks, database risks, business risks.. 它们可能可以按应用程序层划分-Jboss服务器风险,数据库风险,业务风险。

You're going to have to put your storage (database) in read-only mode during the migration. 在迁移过程中,您将必须将存储(数据库)置于只读模式。 The application won't be down but some features that alter the data won't be available. 该应用程序不会关闭,但是某些更改数据的功能将不可用。 During the read-only mode time you copy the data over the new primary site. 在只读模式期间,您将数据复制到新的主站点上。 Once all that data is copied the users must be redirected to the new site and the application becomes read-write again. 复制所有数据后,必须将用户重定向到新站点,并且应用程序再次变为读写状态。

If a read-only mode isn't acceptable then you'll have to maintain two databases in sync. 如果不接受只读模式,则必须维护两个数据库同步。 Products such as GoldenGate can do that for you. 诸如GoldenGate之类的产品可以为您做到这一点。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM