Modeling a Paginated API as a Lazy Stream
You are integrating with a 3rd party application that contains statistics on the most popular baby names for a given year. You have both high-level stats and per-name information you’d like to display. It’d be nice if you could write the code like this: class NamesController < ApplicationController def index @names = Names::Client.all_names end def show @name = Names::Client.find_name(params[:name
Building and testing a Phoenix JSON API
Note: This blog post is for Phoenix 1.2. If you’re on Phoenix >= 1.3 check out the Phoenix guides. Since writing the first version of this guide a lot has changed in Phoenix. In this post we’ll show you how to build and test the index and show actions of a JSON API with Phoenix 1.2. We’ll show you some new techniques we’ve learned since the last time. You’ll learn: How to use the built-in Phoenix
Caching API Requests
When making requests to an external service’s API, some requests will frequently occur with the same parameters and return the same result. If we cache our request or response, we can reduce HTTP requests, which can improve performance and avoid hitting rate limits. The APICache Ruby gem is a good choice for caching the API responses (typically JSON) in any Moneta store, such as Memcache or Redis.
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Backbone.js, JSON API, and Relational Data: A Primer
Build and test a blazing fast JSON API with Phoenix, an Elixir framework
