Planning the Analytics profile and storage

Begin planning your IBM® API Connect Analytics deployment by choosing a deployment profile and a storage class.

Deployment profile

The first decision you must make is which deployment profile you want to use. There are two choices:

  • n1xc2.m16: development profile
  • n3xc4.m16: production profile

The development profile describes a hardware profile of 1 node, 2 cores, and 16 GB memory. This profile deploys a single-node, non-HA, non-scalable Analytics solution. The development profile is only recommend for development and test environments.

The production profile describes a hardware profile of 3 nodes, 4 cores, and 16 GB memory. This profile deploys a three-node, HA, scalable Analytics solution. The production profile requires at least 3 nodes to work properly, and is the recommended option for production environments.

Note: Although you can deploy the development profile to a production environment, it is not recommended. This deployment option was designed to have a small impact on your hardware and as such it will not scale, and it will not perform as well as the production profile.

Storage class

Before installing Analytics, you must choose a storage class. Ceph, Block, and Local Volume are all supported; however, Local Volume is most suitable for Analytics. The Analytics subsystem provides internal data replication and HA support, so the additional HA capabilities that Ceph or Block storage might give you are not needed. In addition, Analytics requires a high throughput of disk I/O operations to successfully handle the analytics data load from the Gateway. Local Volume is the best-performing option in this area.

Note: GlusterFS storage is not supported for Analytics. If you use this option, you might encounter severe performance degradation, and, in some cases, loss of data.

For instructions on specifying a deployment profile and a storage class for your Analytics deployment, see Installing analytics.