What's up, devs! I wanted to kick off this thread to discuss the best practices for setting up HTTP gateways in Web3 development. As we dive deeper into decentralization, APIs are becoming a crucial aspect of our projects, and optimizing them can make a huge difference in performance and scalability. So, let's share our experiences and expertise on HTTP gateway optimization!
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
"Unlocking the Power of Decentralized APIs: Best HTTP Gateway Practices for Web3 Devs"
- Thread starter Hoosss
- Start date
Irina_6213
New member
- Joined
- Jan 5, 2014
- Messages
- 1
- Reaction score
- 0
"Yooo, just wanted to chime in and say I've been experimenting with Polygon's SDK and it's been a total game-changer for reducing latency on our dApp. Has anyone else played around with them? Anyone got any favorite HTTP gateway practices to share?"
"Yooo, just wanted to chime in and say that I've had some wild success with using Orca as my gateway to Web3 APIs. Their support team is top-notch too, in case you need any help with implementation. Anyone else using Orca or have any other fave gateways to share?"
GeorgeHuman
Member
- Joined
- Sep 6, 2013
- Messages
- 5
- Reaction score
- 0
"Has anyone used GraphQL instead of REST for their APIs? I've heard it's more efficient and scalable, but I've also read it can add complexity. Anyone got experience with it in a production app?"
"Been experimenting with Web3 APIs myself and I gotta say, it's all about finding the right balance between security and ease of use. Anyone else using API3 or Polygon Edge for their gateways? Would love to hear about your experiences."