Getting Started with Catalyst Zia Services :

This section covers the overall steps involved in leveraging Zia components in your Catalyst application and building upon them.

1. Create a project : Access the Catalyst console or create a new project. After the project creation is done, you will be able to access all Catalyst services from the console.

   Additionally, you can also create a new project in the local environment by initializing it from the CLI. You must first install Catalyst CLI and log in to your remote account before you can access the Catalyst commands and work with your application locally.

2. Accessing Catalyst Zia Services : You can access Catalyst Zia components by navigating to the Catalyst Zia service in the left pane of the Catalyst console. You can view all text-based and image-based Zia features there, access the component of your choice, and test them instantly with sample data to get a better understanding of their functionality or the responses you would receive.

3. Code the logic : You can easily incorporate these Zia components, and all other required services, into your application’s logic using the Catalyst SDK in your code for the required platform. You can also access a host of Catalyst functionalities through our component-specific API endpoints.

   You can choose to build your Catalyst application by accessing and implementing the required Catalyst components from the other services. You can build the application logic by working with the Catalyst project directory locally using an external IDE. Catalyst CLI enables you to initialize all of your project resources in the local environment directly.

4. Test the application : If you have built your application in Catalyst platform, you can test your application or microservice locally before deploying it to the remote console through a variety of CLI commands. For example, you can test certain function types through a built-in shell in your terminal.

   If you test your application locally, you can deploy it to the remote console after the testing, and access the client and accessible function end-points from their development URL.

   Note : The sequence of steps specified here might differ based on your business or application logic, or your specific use case. The flow mentioned in the deploying and testing phases of the application can be altered based on your requirements. This is a generic set of guidelines that is suitable for a typical small to mid-scale, client-based application or microservice.

5. Host the application : You can also host your Catalyst web application in the development environment in parallel through the web client hosting of the CloudScale service, and monitor its performance. Using Catalyst DevOps, you can perform iterative QA tests, end-to-end integrated tests, or release an alpha version of your solution.

6. Migrate your application to production : After you test your application in the development environment, it can be migrated to production as described in this help page. You can continue using the DevOps components post production to monitor your application during the maintenance phase, as well as during subsequent upgrades and releases.