Catalyst Serverless - A Quick Start Guide

This section covers the overall steps involved in creating and developing your Catalyst applications by leveraging the Catalyst Serverless components. You can engineer, test, and deploy robust applications and microservices of any scale using the various components of Serverless.

  1. Create a Project - Access the Catalyst console to create a new project. After the project creation is complete, you will be able to access all components of Serverless and other Catalyst services from the console.
Note: You can familiarize yourself with the various services and components and gain a more practical understanding of Catalyst by using the step-by-step guide present in the Tutorials section.

Additionally, you can also create a new project in the local environment by initializing it from the CLI. You can initialize project resources like functions, or client services along with the project. 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.

  1. Engineer your application - You can initialize your function components as a Basic I/O,Advanced I/O, Event, Cron, Integration, or Browser Logic. You can then code your application locally using an IDE of your preference.
Note: You can also add new functions in an existing project directory using the Catalyst CLI command: catalyst functions:add.

Catalyst Serverless functions can be coded in:

When you initialize your functions, you can choose the stack and install the required dependencies. A few configuration files pertaining to Catalyst will also be installed in your local project directory.

You can refer the code templates present in Catalyst SDKs to incorporate Catalyst CloudScale components in your application, such as for backend functionalities like database, storage, caching, etc and build anything from a simple microservice to a robust enterprise application. There are exclusive SDKs present for each of the supported programming languages, and you also have SDKs available for engineering Web, Android, iOS, and Flutter applications.

Addionally, you can employ Circuits to orchestrate your applications workflow from the console. Security Rules will contain default security definitions for your Basic I/O and Advanced I/O functions.

You can also build and deploy your application or service as an AppSail solution as an entire package. The PaaS component enables you to develop solutions independent of Catalyst and simply host them onto the platform.

  1. Test your application - You can test your project resources like the functions or AppSail locally using the catalyst serve CLI command. You can also test the endpoints of your application by accessing them through their catalyst-generated URLs, or test functions by launching a shell for functions by using the CLI command catalyst functions: shell.

  2. Deploy to console - Deploy your project resources to the console from the CLI using the catalyst deploy command after you test them locally. You can also upload functions directly in the console.

  3. Log and Monitor - You can now avail the components of Catalyst DevOps to log and monitor your function. You can also secure your function endpoints, and perform all operations management tasks with DevOps.

  4. Deploy to production - When your application or microservice is ready to be deployed, you can migrate your resources to the production environment.

You can continue to monitor your applications with Catalyst DevOps.

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.

Last Updated 2023-09-02 13:42:08 +0530 +0530