 |
| Global Architecture Imperatives guide the design and implementation of applications so that they can support global requirements. |
|
|
| Designing and developing applications that have a single executable, support Unicode, and utilize localization packs within a locale model will make it easy to create customer-facing applications for users from all over the world. However, most companies have applications that have been developed and data that have been collected over a long period of time it is not practical to convert them all to the new architecture. The challenge is how to provide a global user experience while maintaining the existing applications and data.
There is no single solution that fits all situations. The actual solution will vary from one company to another. For companies who do not have a lot of legacy systems, rewriting everything based on the GAI is a viable option. But for others it is neither practical nor affordable. One approach would be to keep existing applications as they are and use connectors to connect them to updated customer-facing modules. Depending on the existing applications and data, it may be necessary to have multiple databases, one for each script, and the applications also may need to be modified. This may require some changes to the existing applications but the work will be significantly easier than developing new applications from scratch. For companies that have their data primarily in English, keeping the data in UTF-8 and modifying the applications can also be considered.
It is important to understand the options available and to plan the integration carefully. |
|
|
| | |
