Should we remove redundant endpoints from Catalyst? ll

by 0x6438c3b1fa97ba144ea38fcbcee5f0ccf4539b1d (ph33bs)

Introduction

The Lambdas service from Catalyst was originally designed to support various independent operations required by the reference implementation client. However, as time progressed, newer and more effective endpoints with identical functions were introduced, yet the service retained all previous iterations.

This is the second of a serie of proposals that aim to enhance the resilience and efficiency of Catalyst's Lambdas service by optimizing its endpoints and removing old implementations that didn't take performance into consideration, making inefficient use of resources. You may find the first proposal of this serie here.

The main objective of this proposal is to decrease the overhead of the Lambdas service and improve Catalyst response times by removing the redundant endpoints GET /lambdas/contentv2/contents/:cid, GET /lambdas/contentv2/scenes, and GET /lambdas/contentv2/parcel_info.

Proposal

GET /lambdas/contentv2/contents/:cid

This endpoint is currently acting as a proxy, forwarding the initial request to the GET /contents/:cid endpoint of the Content service and returning its response without any additional formatting. Going forward, clients should access the GET /content/contents/:cid endpoint from content-server directly.

GET /lambdas/contentv2/scenes

This endpoint is currently acting as a proxy, forwarding the initial request to the POST /content/entities/active endpoint of the content-server and returning its response without any additional formatting. Going forward, clients should access the POST /content/entities/active endpoint from content-server directly.

GET /lambdas/contentv2/parcel_info

This endpoint is also acting as a proxy, forwarding the initial request to the POST /content/entities/active endpoint of the content-server and returning its response without any additional formatting. Going forward, clients should access the POST /content/entities/active endpoint from content-server directly.

Provided that this proposal gets general acceptance level, the specified endpoints will be removed one month subsequent to its approval.

• Delete the endpoints
• Keep the endpoints
• Invalid question/options

This proposal is summarized due to technical limitations. To view it complete and vote on it, visit the DCL DAO Governance dApp