Why REST API for predictions in TensorFlow? - Purpose & Use Cases

The Big Idea

What if your AI model could answer questions from anywhere in the world instantly, without any setup?

The Scenario

Imagine you built a smart model that can tell if a photo has a cat or a dog. Now, you want your friends to use it anytime from their phones or websites. But you have to send them the model file and explain how to run it on their computers.

The Problem

This manual way is slow and confusing. Your friends might not have the right setup, or they could make mistakes running the model. It's hard to update the model for everyone, and sharing results takes too long.

The Solution

Using a REST API for predictions means your model lives on a server. Your friends just send a photo over the internet, and the server quickly sends back the answer. No setup, no confusion, and updates happen instantly for all users.

Before vs After

✗ Before

load_model('model.h5')
predict(image)

✓ After

POST /predict {"image": ...}
Response: {"label": "cat"}

What It Enables

It makes your smart model instantly available to anyone, anywhere, on any device, with just a simple internet request.

Real Life Example

Apps like voice assistants or photo filters use REST APIs to send your voice or picture to a server and get smart answers back in seconds.

Key Takeaways

Manual sharing of models is slow and error-prone.

REST APIs let you serve predictions easily over the internet.

This approach makes your AI accessible and simple for everyone.

Practice

1. What is the main purpose of creating a REST API for a TensorFlow model?

easy

A. To save the model in a different file format

B. To train the model faster on a server

C. To visualize the model's architecture

D. To allow other programs to send data and get predictions easily

Solution

1. Step 1: Understand REST API role

   A REST API acts as a bridge to send data and receive results from a model.

2. Step 2: Match purpose with options

   Only To allow other programs to send data and get predictions easily describes this role correctly as it enables easy data exchange for predictions.

3. Final Answer:

   To allow other programs to send data and get predictions easily -> Option D

4. Quick Check:

   REST API purpose = Easy data exchange for predictions [OK]

Hint: REST API = send input, get output from model [OK]

Common Mistakes:

• Confusing API with training process
• Thinking API is for visualization
• Assuming API changes model files

2. Which Flask code snippet correctly defines a POST endpoint to receive JSON input for predictions?

easy

A. app.post('/predict')\ndef predict():\n data = request.get_json()

B. app.route('/predict')\ndef predict():\n data = request.get_json()

C. app.route('/predict', methods=['POST'])\ndef predict():\n data = request.get_json()

D. app.get('/predict')\ndef predict():\n data = request.get_json()

Solution

1. Step 1: Identify correct Flask route syntax for POST

   Flask uses @app.route with methods=['POST'] to define POST endpoints.

2. Step 2: Check code snippets

   Only app.route('/predict', methods=['POST'])\ndef predict():\n data = request.get_json() uses @app.route with methods=['POST'] and calls request.get_json() correctly.

3. Final Answer:

   app.route('/predict', methods=['POST'])\ndef predict():\n data = request.get_json() -> Option C

4. Quick Check:

   Flask POST route = @app.route with methods=['POST'] [OK]

Hint: Flask POST = @app.route with methods=['POST'] [OK]

Common Mistakes:

• Using app.post decorator (not standard Flask)
• Missing methods=['POST'] in route
• Using app.get for POST requests

3. Given this Flask code snippet, what will be the output if the input JSON is {'input': [1, 2, 3]} and the model predicts sum of inputs?

from flask import Flask, request, jsonify
app = Flask(__name__)

@app.route('/predict', methods=['POST'])
def predict():
    data = request.get_json()
    inputs = data['input']
    prediction = sum(inputs)
    return jsonify({'prediction': prediction})

medium

A. {"prediction": 6}

B. {"prediction": [1, 2, 3]}

C. {"prediction": 123}

D. Error: KeyError

Solution

1. Step 1: Extract input and compute prediction

   The input JSON has 'input': [1, 2, 3]. The code sums these values: 1+2+3=6.

2. Step 2: Return prediction as JSON

   The code returns jsonify({'prediction': 6}), so output is {"prediction": 6}.

3. Final Answer:

   {"prediction": 6} -> Option A

4. Quick Check:

   Sum([1,2,3]) = 6 [OK]

Hint: Sum input list to get prediction output [OK]

Common Mistakes:

• Returning input list instead of sum
• Concatenating numbers as string
• Misreading JSON keys causing KeyError

4. You wrote this Flask API code but get an error when sending POST requests. What is the likely cause?

from flask import Flask, request, jsonify
app = Flask(__name__)

@app.route('/predict')
def predict():
    data = request.get_json()
    prediction = model.predict(data['input'])
    return jsonify({'prediction': prediction.tolist()})

medium

A. model.predict() cannot accept JSON data

B. Missing methods=['POST'] in @app.route decorator

C. request.get_json() only works with GET requests

D. jsonify() cannot convert lists

Solution

1. Step 1: Check route decorator for HTTP methods

   The route lacks methods=['POST'], so it defaults to GET only, causing errors on POST requests.

2. Step 2: Confirm other parts are correct

   model.predict() can accept arrays, get_json() works with POST, and jsonify converts lists fine.

3. Final Answer:

   Missing methods=['POST'] in @app.route decorator -> Option B

4. Quick Check:

   POST route needs methods=['POST'] [OK]

Hint: Add methods=['POST'] to route for POST requests [OK]

Common Mistakes:

• Forgetting to specify POST method in route
• Assuming get_json works only with GET
• Thinking jsonify can't handle lists

5. You want to deploy a TensorFlow model with a REST API that accepts multiple inputs and returns predictions for each. Which approach is best to handle batch inputs in your Flask API?

hard

A. Accept a JSON list of inputs, convert to numpy array, predict batch, return list of predictions

B. Accept one input at a time, call model.predict repeatedly for each

C. Save each input to a file, then load and predict later

D. Use GET requests with inputs in URL parameters

Solution

1. Step 1: Understand batch prediction needs

   Batch prediction means processing many inputs at once for efficiency.

2. Step 2: Choose method to handle batch inputs

   Accept a JSON list of inputs, convert to numpy array, predict batch, return list of predictions accepts JSON list, converts to array, predicts all at once, then returns all predictions, which is efficient and standard.

3. Final Answer:

   Accept a JSON list of inputs, convert to numpy array, predict batch, return list of predictions -> Option A

4. Quick Check:

   Batch input = JSON list + batch predict [OK]

Hint: Batch predict by sending list and returning list [OK]

Common Mistakes:

• Predicting one input at a time (slow)
• Using files instead of direct JSON
• Using GET for large input data