V1 - V2 Migration Guide

For those on Banana before July 2023

We understand that change can sometimes be challenging, but with this guide, we aim to make your migration process as smooth as possible.

We'll walk you through the necessary steps and highlight the key differences between the two versions, enabling you to adapt your models to the enhanced features and capabilities offered by V2.

Who should use this guide

This guide is only relevant for users on Banana that have created an account before 19th June 2023. If you joined later you're by default on V2.

Why V2 is better than V1

Banana V2 is an upgrade to make the platform faster, more reliable & usable. The key areas that are we've focused on are:

  • ⚡ Speed: the average latency added by Banana is 100ms

  • ⚙️ Reliability: a global uptime of 99.99%

  • 💻 Usability: your model behaves remotely in the same way as locally


  • New users have increased pricing on V2, you'll maintain your existing price if you migrate before the deadline

  • V2 supports up to 1mb payloads, this is so we can keep the middleware fast. If your payload (request or response) being sent from SDK to banana is >1mb you'll need to upload your responses to a third party storage and return a reference to that store. We talk about how to do this in Configuring Potassium

  • Our V2 backend doesn't have a queue built in, instead our SDKs will retry calls if they don't have an available replica. This is functionally the same for you and gives you more control to build out your own queueing logic if you choose.

What to expect

We'll go through a step-by-step migration process, using a simple BERT model as an example. It should take about 10 minutes to read through and you can deploy the BERT on V2 while reading the guide.

Let's go! 🚀

Last updated