Skip to content

Should we remove redundant endpoints from Catalyst?

PassedPoll

Proposal Details

Author0x6438…9b1d
PublishedMay 05, 2023 14:21
Voting beginsMay 05, 2023 14:21
Voting endsMay 10, 2023 14:21
Snapshot#70d446b

Description

### 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 first 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. The main objective of this proposal is to decrease the overhead and improve the functionality of the Lambdas service by removing the now obsolete GET /lambdas/health and the redundant GET /lambdas/profile endpoints. ### Proposal **GET /lambdas/health** This health endpoint was designed to handle the responsibility of reporting the status of every catalyst service, which was not an appropriate use case, thereby it will be replaced with the [Realm-Description /about endpoint](https://decentraland.github.io/catalyst-api-specs/#tag/Global/operation/getAboutCatalystInfo) specified on [ADR-110: Realm description](https://adr.decentraland.org/adr/ADR-110). **GET /lambdas/profiles** The usage of this endpoint can be replaced by [POST /lambdas/profiles](https://decentraland.github.io/catalyst-api-specs/#tag/Lambdas/operation/getAvatarsDetailsByPost) which has no limitations regarding the amount of profiles you can request. From now on, the IDs to be included in the request body instead of as query strings. This change aims to address the URL length limitation issue and allow clients to request multiple profiles simultaneously, thereby enhancing the versatility and scalability of the service. Provided that this proposal gets general acceptance level, the specified endpoints will be removed one month subsequent to its approval.

10 Comments

daoMay 16, 2023

Should we remove redundant endpoints from Catalyst? This proposal has been PASSED by a DAO Committee Member (0xbef99f5f55cf7cdb3a70998c57061b7e1386a9b0)

daoMay 10, 2023

Should we remove redundant endpoints from Catalyst? This proposal is now in status: FINISHED. Voting Results: * Delete the endpoints 100% 6,312,478 VP (85 votes) * Keep the endpoints 0% 0 VP (0 votes) * Invalid question/options 0% 0 VP (0 votes)

MorrisMustangMay 09, 2023

This is a great idea. I echo everyones sentiments about reducing complexity and not having to support endpoints producing duplicate data. Also a fan of removing the limitation that was inherent of url character length.

ph33bsMay 08, 2023

Hello @dax, Nice to see you involved on this proposal. Yes, we can agree on that, if the proposal passes we are deleting these endpoints on June 15th.

daxMay 07, 2023

agree with this - @ph33bs could we say the deprecation date is june 15th?

HPrivakosMay 06, 2023

Sounds good to me, no reason to keep outdated endpoints when there are replacements. No features are being removed and it will prevent the team having to uselessly spend time on maintaining them. It would be nice to have a set date to deprecate those endpoints so services still using them know before when to migrate.

CanessaMay 06, 2023

This is above my paygrade, so I will wait for more experienced developers to weigh in on how this would affect Decentraland before voting.

agusaldasoroMay 05, 2023

We definitely should remove those endpoints in order to keep Lambdas Service as simple as needed!

web3nitMay 05, 2023

Thanks for proposal. Would be nice to hear thoughts of Community members with technical background. Hey Folks :wave: What do you think about it ? @dax @AwedJob @HPrivakos @szjanko @MorrisMustang

ph33bsMay 05, 2023

**About the author** I’m Alejo Ortega, a back-end developer contributing to the Decentraland Foundation in the area of Catalyst Development. This proposal was co-authored with Matias Penthreath and Hugo Arregui.