Database Networking on Clouddley Triggr

Learn about database networking on Triggr

Database networking determines how your database communicates with applications and other services. Clouddley Triggr provides detailed configurations for public and private networks, allowing users to use the best option based on their needs. This article covers the key differences and how to select the appropriate database network type on Clouddley Triggr.

Understanding public and private networks

Understanding the differences between public and private networks helps ensure the right database networking choice is made based on security, performance, and accessibility requirements.

Public Network

A public network allows external access to a database over the Internet, enabling remote connections for external applications and third-party integrations. However, it increases exposure to security threats, requiring strict measures such as IP whitelisting, firewall rules, and encryption. Additionally, internet traffic may introduce latency.

Private Network

A private network keeps database connections within a secured environment, preventing direct internet access. It supports internal communication, microservices architectures, and enterprise systems with strict security policies. This setup reduces exposure to unauthorized access, improves connection speed and reliability, and enhances access control within a controlled environment.

Is your application deployed on Clouddley Triggr? If yes, read this!

This applies only when your application and database are deployed on Clouddley Triggr and you want to connect them over the private network.

Step 1: Use the ports below to connect your application to the database over the private network. Don’t use the ports shown on the Private Network tab.

Database	Port
MySQL	3306
PostgreSQL	5432
Redis	6379
MariaDB	3306
MongoDB	27017

Step 2: When configuring the connection, set your database name as the host to ensure the private network connection works properly.

The database name is the one you configured when creating your database on Clouddley Triggr.

The database name in your database’s Overview tab.

Database Network Settings on Clouddley Triggr

Clouddley Triggr provides details for both public and private networks, allowing users to utilize them as needed for their database connections.

Database networking connections tab.

Choosing the Right Network Type

Users can use both public and private networks depending on their needs:

• Public networks are useful for remote access and integrations.

• Private networks offer secure, internal connectivity.

Using the Public Network

1. Retrieve the public connection details from Clouddley Triggr.

Using the Private Network

1. Retrieve private network details from Clouddley Triggr.

2. Ensure internal applications and services have the correct network permissions.

3. Use private IP addresses or VPC peering for secure connections.

Conclusion

Clouddley Triggr provides users with public and private network details, ensuring flexibility in database connectivity. Public networks allow external access but require strict security controls, while private networks enhance security by keeping connections internal. By implementing best practices such as access restrictions and encryption users can maintain a secure and optimized database network.