Using wso2 carbon logging to store configuration data for SOA services

Question

I have several different SOA services that use different approaches to store configuration data for a service. For example, configuration data is stored in database tables, property files, and jndi.

I would like to standardize my approach to storing configuration data. Is the carbon register an acceptable place to store all configuration data for my services?

Can I just store this data directly in the carbon registry, or should I just use the WSO2 management registry for this data?

What does the WSO2 Governance Registy register that is not provided directly using the carbon registry?

Answer 1

"Is the carbon register an acceptable place to store all configuration data for my services?"

The best practice would be, Store the resource metadata in the registry and the run-time data in the database.

Is the carbon register an acceptable place to store all configuration data for my services? "

Yes, you can save the configuration in the registry. Typically, configurations will be stored in the configuration space, and resources that have a management aspect will go into the management registry area.

"What does the WSO2 management registry give me that are not provided directly using the carbon registry?

• Store, manage, and search for any type of enterprise asset, including services, APIs, policies, projects, or applications. You can distribute predefined asset metadata or create your own
• Asset movement using taxonomy
• Access and asset management through a REST API that supports integration with a corporate initiative, such as DevOps
• Describe the relationship between the assets, such as dependencies, usage, or associations, and perform an impact analysis.
• Associate an individual life cycle with assets and activate custom actions when an asset moves from one state to another.
• Protect access to assets with the small model.
• Use social tools such as ratings and comments to provide a better connection between asset providers and consumers.
• Notify users of any asset changes via email or the notification system of your choice.
• Integration with mediation mechanisms such as WSO2 Enterprise Service Bus or others using UDDI and REST to dynamically discover services and API endpoints.

There are many benefits to using G-Reg. To view the full list, look for the post or offcial G-Reg Page .