Should we remove redundant endpoints from Catalyst? lll

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 third 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 and second proposal of this serie here and here, respectively.

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

Description

The main objective of this proposal is to enhance the functionality and usability of the Lambdas service by replacing the GET /lambdas/collections/wearables-by-owner/:address endpoint with the GET /lambdas/users/:address/wearables endpoint.

Proposal

GET /lambdas/collections/wearables-by-owner/:address

This endpoint will be replaced with GET /lambdas/users/:address/wearables which returns the same data but paginated. This change increases the versatility and scalability of the Lambdas service.

• Delete the endpoint
• Keep the endpoint
• 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