User interface platform integrated-development system and method having microservice architecture
A user interface platform integrated-development system and method having a microservice architecture are disclosed. A user interface platform development system according to one embodiment of the present invention may comprise: a development tool, which provides a WYSIWYG-type screen file development environment to generate a screen file source in which a user interface platform is formed into a structured component; a server for providing resources for screen file development through the development tool, and registering the developed screen file source; and a client which includes a client engine for loading the screen file source requested by the server and received as a response, and which executes same in a browser window to provide the user interface platform corresponding to a connected device.
1 . A user interface platform development system, comprising:
a development tool, configured to provide a What You See Is What You Get (WYSIWYG)-style screen file development environment and generating a screen file source that organizes an user interface platform with structured components;
a server, providing resources for developing a screen file with the development tool, and with which developed screen file sources are registered; and
a client, having a client engine to load the screen file source that is received from the server, and configured to execute in a browser window to provide the user interface platform according to an associated device,
wherein the client comprises a cross-Microservice Architecture (cross-MSA) resource sharing module configured to fetch resources from a plurality of servers,
wherein when the cross-MSA resource sharing module fetches resources and an msaName is set, a service domain is selected by referring to msaServer in a configuration file, and the resources are fetched from the selected service domain, and
wherein when the cross-MSA resource sharing module fetches resources and the msaName is not set, the system searches a high level page where the msaName is set, selects a domain from the high level page using the msaName, and the resources are fetched from the selected domain.
2 . The user interface platform development system of claim 1 , wherein the structured components comprise at least one of Page component, user defined component (UDC), Project UDC, and Microservice Architecture (MSA) UDC.
3 . The user interface platform development system of claim 1 , wherein the client comprises a Microservice Architecture (MSA) message broker configured to correspond to a microservice architecture and a micro frontend architecture having a cross-MSA resource sharing function.
4 . The user interface platform development system of claim 1 , wherein when the cross-MSA resource sharing module fetches resources of Cascading Style Sheets (CSS) from a domain other than the service domain selected by referring to msaServer in the configuration file, a Syntactically Awesome Style Sheets (SASS) preprocessor compiles the CSS to process images defined within the CSS to prevent 404 errors.
5 . The user interface platform development system of claim 3 , wherein the client comprises a Microservice Architecture (MSA) message broker module configured to remove dependency between User Interface (UI) elements and exchanging data between services, wherein the MSA message broker is implemented in hub-and-spoke method.
6 . The user interface platform development system of claim 5 , wherein the MSA message broker registers message channels in page components to be used as project User Defined Components (UDCs).