The following are important concepts and approaches for building optimal integrations to Swarm.

...

The Content Gateway is used to handle redirects internally and allows using it with a modern HTTP library or S3 SDK using SCSP or S3 API rather than connecting an application directly to Swarm nodes. Gateway provides additional functionalities such as authentication, authorization, and Swarm node connection pooling.

For example –: It is suggested to use the popular ‘requests’ library with Python. Use the official AWS SDKs on Java, C#, or Go programming language if an application uses the S3 API. Or to make SCSP requests, use a standard HTTP library like Apache HttpClient on Java.

...

The Content-MD5 header provides an extra level of insurance, protecting against potential damage in transit as well as from damage while in storage.

See Configuring Swarm Storage for configuration parameters and how to edit the configuration files.

See Content-MD5 Checksums.

See Lifepoint Metadata Headers for more information about lifecycle management.

See Content Integrity Assurance.

Use Multithreading

Swarm is a multithreaded, multi-node cluster. Every node in a storage cluster can establish and maintain connections with many different client applications at the same time. Normally an application opens one SCSP connection to the cluster and sends requests and receive responses in a sequential manner. A single client application may choose to open more than one connection to Swarm to achieve better response times and read or write throughput for high-volume applications.

...

• Close the old connection before opening the new, redirected connection.

• Maintain a pool of connections to several nodes in the cluster. The pool approach can considerably improve response times because the client eventually has open connections to all nodes for smaller clusters.