Edge for Private Cloud v. 4.17.09
Using a Load Balancer
A production installation of API BaaS uses a load balancer between the API BaaS Portal node and API BaaS Stack nodes. When configuring the Portal, you specify the IP address or DNS name of the load balancer, not of the Stack nodes.
As an alternative to a load balancer, you could use round-robin DNS. In this scenario, you create a DNS entry with multiple A records corresponding to BaaS stack IP addresses. During a DNS lookup, the DNS server automatically returns A record values in a round robin fashion.
Connecting to Cassandra
When installing BaaS, you can choose to connect BaaS and Edge to the same Cassandra cluster, or create a separate Cassandra cluster for BaaS. Smaller BaaS installations, meaning those with lower traffic volumes, often share a Cassandra cluster with Edge.
For the high throughput and availability, or to separate Cassandra clusters into different network zones, Apigee recommends that you use separate Cassandra clusters. Separate clusters maximize performance if you are experiencing high traffic loads on BaaS.
You must have the date/time on all servers synchronized. If not already configured,
ntpdate utility could serve this purpose, which verifies whether servers are time
synchronized. You can use
yum install ntp to install the utility.
The API BaaS installer also installs the Apache Tomcat server on all API BaaS Stack nodes, including the Tomcat administrator UI. The installer leaves the default administrator credentials unchanged from admin:admin.
If necessary, you can change these credentials as part of securing Tomcat. For more information, see:
Installing BaaS in multiple data centers
You can install API BaaS across multiple data centers. The typical procedure is: