ROMA Connect Best Practices

This document summarizes best practices for common application scenarios using ROMA Connect. Each case includes a detailed solution description and operational guidance, enabling you to easily build your services with ROMA Connect.

**Table 1** ROMA Connect best practices
Practice	Description
Digitalizing the Traditional Parking Lot Management System	ROMA Connect digitizes parking lot systems for smarter management.
Sharing Enterprise Data Using APIs	ROMA Connect APIC opens databases as RESTful APIs, so that data between different service systems can be shared through APIs. Multiple security authentication modes are available to secure access of application system data across networks and regions.
Integrating and Converting Service Data Across Systems	ROMA Connect FDI converts the format of data in service system A and integrate the data into the database of service system B, and synchronize new data between the two systems periodically according to a preset plan.
Configuring the Service Opening Platform	The API cascading capability of APIC cascades the APIs of the ROMA Connect instances of subsidiaries A and B to the ROMA Connect instance of the HQ. The ROMA Connect instance of the HQ is used as the service openness platform. All digital assets are shared externally through the service openness platform.
Developing a Custom Authorizer with a Custom Backend	ROMA Connect APIC quickly encapsulates existing backend services, data sources, and user-defined functions into RESTful APIs, and then exposes the APIs to external systems, streamlining the interconnection between service systems and lowering the costs.
Avoiding MQS Message Accumulation	Accumulation can be avoided by the consumer, producer, and server.
Synchronizing Data from MySQL to Oracle as Scheduled	A composite application template is available for this purpose by automatically capturing the latest data records in MySQL and synchronizing them to Oracle.