Skip to content

General Requirements

This section outlines the necessary requirements for installing and running a single (non-clustered) instance of Backendless Pro. The requirements are categorized into general prerequisites applicable to all installations and specific ones tailored to different operating systems or cloud environments.

Instance Requirements for Optimal Performance

To successfully deploy and run the Backendless Pro Community Edition, aligning your system with the right specifications is crucial for achieving both baseline functionality and an enhanced operational experience. The guidance provided below outlines the necessary and recommended system requirements to ensure your Backendless Pro deployment is efficient and effective.

Minimum System Requirements

Ensure your system meets the following specifications for basic functionality:

  • Memory: A minimum of 8 GB of RAM is required to support the various operations and processes within the Backendless ecosystem effectively.
  • CPU: At least 4 CPU cores are recommended to ensure sufficient processing power for handling multiple tasks simultaneously and maintaining overall system responsiveness.
  • Disk Space: A minimum of 20 GB of available disk space is necessary to accommodate the initial setup and data storage needs for Backendless services and databases.

For optimal performance, particularly with larger scale projects or more complex applications, consider the following system upgrades:

  • Memory: Upgrading to 16 GB of RAM is recommended to enhance performance capabilities, enabling smoother operation of Backendless services, improved data processing, and better management of concurrent requests.
  • Disk Space Extension: Starting with 20 GB of disk space meets the basic requirement, but the ability to expand this capacity is essential as your application and its data storage needs grow. Planning for scalable storage solutions ensures that increasing data from your application, including user data and media files, can be accommodated without impacting performance or risking data loss.
Important Note

It's essential to understand that these specifications serve as a guideline. The final configuration of your system should be determined in an imperative manner, through comprehensive load testing. This process involves simulating various operational loads to understand how your application performs under different conditions. Load testing will help you identify the optimal configuration that meets your specific usage patterns and requirements, ensuring that your Backendless Pro Community Edition deployment is both resilient and efficient.

By engaging in load testing, you can tailor your system's setup to match your application's demands accurately, ensuring a balance between resource availability and cost efficiency. This proactive approach allows for a customized environment that can handle your operational needs, providing a smooth and reliable experience for your users.

Network Configuration and Port Allocation

Ensure the following ports are available on your system before installing Backendless Pro Community Edition to avoid conflicts:

  • 80/443: This ports are used by Kubernetes Ingress as entry points for handling incoming requests to your services. They play a crucial role in routing external traffic to Backendless workloads like bl-server, bl-web-console, bl-rt-server, and others. These ports ensure that your services can be accessed externally via specified domains, with the Ingress controller managing the routing and security of incoming requests. Proper configuration of these ports and the associated Ingress resources allows for efficient and secure traffic management for your installation.

  • 5050: This port is dedicated to the Pro Manager web server, which hosts the User Interface (UI). The UI is a critical component for managing and configuring your Backendless environment, providing a graphical interface for ease of operation.

  • 5051: Utilized by the Pro Manager for web socket connections, this port enables real-time log streaming and other dynamic updates. This feature is vital for live monitoring of your application's performance and behavior, facilitating immediate responsiveness to events as they occur.

  • 32300: Designated for the Backendless API endpoint, port 32300 is a primary communication channel for your applications to interact with the Backendless services. Ensuring this port is open and conflict-free is essential for the seamless operation of your application's backend functionalities.

  • 32400: This port serves the Backendless Console web server, which is an administrative interface for the Backendless platform. Through the console, users can access a wide range of tools and settings for application management, analytics, and more.

  • 32600: Dedicated to Consul, which is used for managing configuration values within the Backendless ecosystem. Consul plays a critical role in service discovery and configuration, making this port essential for the coherent operation of distributed services and microservices within your Backendless deployment.

Check Port Availability: Use network tools or command-line utilities to confirm these ports are not used by other applications. If conflicts exist, reconfigure the conflicting applications or adjust Backendless Pro's port settings accordingly for a smooth installation.