Because communication to ECS is through HTTP/HTTPs, it is best practice to keep in mind the back and forth traffic or how to mitigate traffic issues within your application.
- Use pre-signed URLs. ECS supports pre-signed URLs to enable users to access objects without needing credentials.
- Object update frequency should be low since object storage platforms are not designed for transactional workloads but ideally for static content such sensor data, images, videos.
- Only one application should write to each bucket. Other applications may read from them, but not write.
- Use the object copy operation instead of downloading and uploading the object again.
- Beware of the concurrent requests for the same object.
- If order needs to be guaranteed, use Conditional PUTs (ECS extensions).
- If there is no external load balancing in your ECS deployment, implement client-side load balancing to distribute load across ECS nodes for increased performance.
- Use “Range Reads” for listing objects. Align the range to your application and request only what is needed. There are “Markers,” “NextMarker,” and “MaxKeys” parameters available to paginate listings.