make any sense to create an API with Go since the backend, as I understand it, will still do the hard work 🤔
I couldn't find a definitive answer with Google.
Does that mean that if I wanted to optimize the API by writing in it Go then both the backend and the API would need to be in Go?
I feel like you'll be bottlenecked a lot more just by Trello's API response times
Because even if the request and response are handled fast, it'll still depend on NodeJS to perform the operations the request asked to
And what are those operations?
The Trello API is virtually a Kanban, so the Trello API can return a (nested) JSON object of all the information in it, or the information in a specific column. One of my automations add a deadline to the cards that don't have it yet. Another automation takes all the cards in a certain column and sends them off to another column located in another board. These type of features are far beyond what you can do natively with the Trello API, so my API would allow you to perform such automations in your boards via my API, so you don't have to write them from scratch yourself. My API -> Node backend -> Trello API Does that make sense?
None of that sounds CPU intensive
Обсуждают сегодня