<commit_before>-   [Home](../../index.md)
-   [Documentation](../index.md)
-   Common KAAZING Gateway Production Topologies

Common KAAZING Gateway Production Topologies
========================================================================

This topic describes some of the most common production topologies for the KAAZING Gateway. It is intended to familiarize network administrators and systems software developers with general KAAZING Gateway production deployments. Your actual production deployment of the Gateway will likely be some variation of the topologies covered here.

All of the topologies in this topic begin with clients on one end and the back-end service or message broker at the opposite end of the connection. It is the number and configuration of Gateway instances between the clients and the back-end service or message broker that distinguishes each Gateway topology.

Developers that want to develop against the Gateway can run the Gateway locally as described in [Setting Up the Gateway](../about/setup-guide.md).

**Note:** Most topologies use Gateway clustering and load balancing. For information on using these features, see [Configure the Gateway for High Availability](../high-availability/o_high_availability.md).

This topic covers the following information:

-   [DMZ to Trusted Network Topology](#dmz-to-trusted-network-topology)
    -   [Deploying the DMZ to Trusted Network Topology](#deploying-the-dmz-to-trusted-network-topology)
-   [Enterprise Shield™](#enterprise-shield™-)
-   [Virtual Private Connection](#virtual-private-connection)
-   [TLS/SSL Security Considerations](#tlsssl-security-considerations)

DMZ to Trusted Network Topology<commit_msg>Update c_topologies.md<commit_after>-   [Home](../../index.md)
-   [Documentation](../index.md)
-   Common KAAZING Gateway Production Topologies

Common KAAZING Gateway Production Topologies
========================================================================

This topic describes some of the most common production topologies for the KAAZING Gateway. It is intended to familiarize network administrators and systems software developers with general KAAZING Gateway production deployments. Your actual production deployment of the Gateway will likely be some variation of the topologies covered here.

All of the topologies in this topic begin with clients on one end and the back-end service or message broker at the opposite end of the connection. It is the number and configuration of Gateway instances between the clients and the back-end service or message broker that distinguishes each Gateway topology.

Developers that want to develop against the Gateway can run the Gateway locally as described in [Setting Up the Gateway](../about/setup-guide.md).

**Note:** Most topologies use Gateway clustering and load balancing. For information on using these features, see [Configure the Gateway for High Availability](../high-availability/o_high_availability.md).

This topic covers the following information:

-   [DMZ to Trusted Network Topology](#dmz-to-trusted-network-topology)
    -   [Deploying the DMZ to Trusted Network Topology](#deploying-the-dmz-to-trusted-network-topology)
-   [Enterprise Shield™](#enterprise-shield--)
-   [Virtual Private Connection](#virtual-private-connection)
-   [TLS/SSL Security Considerations](#tlsssl-security-considerations)

DMZ to Trusted Network Topology
{'fraction_non_alphanumeric': 0.10784601821921834, 'fraction_numerical': 0.0, 'mean_word_length': 5.078571428571428, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1539537', 'n_tokens_mistral': 856, 'n_tokens_neox': 784, 'n_words': 370}