Hackle Proxy (Deprecated)

This document provides instructions for installing and using Hackle Proxy.

If you are using a development platform supported by the SDK, using the SDK is recommended.

1. Overview

Hackle Proxy is a standalone service for centrally calling the Hackle service. You can use the features provided by the Hackle SDK through the Proxy REST API.

1690

2. When should I use Hackle Proxy?

If your development platform is not supported by the Hackle SDK, you can integrate using Hackle Proxy. If an SDK is available for your development platform, using that SDK is recommended. In special cases such as PHP, it may be used alongside an SDK.

You can find the list of development platforms supported by the SDK in the SDK documentation.

3. Best Practices

These are best practices for situations that generally need to be considered, though they may vary by circumstance.

3.1 How many Proxy instances should I deploy?

Generally, the Proxy is implemented to scale from low-spec hardware. For a stable configuration, it is recommended to deploy at least 2 instances.

3.2 Using a Load Balancer

It is recommended to use a load balancer for traffic routing to enable stable scaling of Proxy instances. If you use AWS, you can use AWS Elastic Load Balancer to stably scale Proxy instances as internal traffic increases.