API BaaS Deprecation and End of Life

Apigee is deprecating the Apigee Edge API Backend-as-a-Service (API BaaS) feature, which includes the ability to use Android push notifications.

The API BaaS end of life (EOL) will be June 30, 2019. Apigee will continue to operate and support API BaaS until June 30, 2019, subject to the terms of our deprecation policy.

In addition, the Android push notifications functionality is reliant on Google Cloud Messaging (GCM), which will reach end of life on April 11, 2019. We recommend that Android push notification customers start their planning to migrate off of Apigee API BaaS for this functionality before April 11, 2019.

What changes are being made?

In May 2018, we announced that API BaaS is being deprecated and will reach end of life (EOL) on June 30, 2019.

In addition, Google Cloud Messaging (GCM) will reach end of life on April 11, 2019. API BaaS Android push notifications rely on GCM, and will not be upgraded to GCM's replacement, Google Firebase Cloud Messaging (FCM).

Why are we deprecating API BaaS?

When Apigee launched Apigee API BaaS (based on the open source Apache Usergrid) in 2012, it was solving for an array of challenges for mobile app developers within one product. Now that Apigee is part of Google Cloud Platform, customers can take advantage of a variety of best-in-class, widely adopted technologies for each of the use cases that Apigee API BaaS addressed (some users are already exploring this).

GCP products, including Cloud Firestore, Cloud Datastore, Cloud Spanner, Cloud SQL, and Firebase Cloud Messaging, provide a range of solutions that go well beyond the capabilities of Apigee API BaaS.

What actions do I need to take?

You must export or migrate data from API BaaS before June 30, 2019. If you are using API BaaS Android push notifications, we recommend you migrate from API BaaS before April 11, 2019, when Google Cloud Messaging (on which Android push notifications rely) is deprecated.

Are there any GCP alternatives for migrating from API BaaS?

GCP has a number of database solutions for customers to consider:

  • Google Cloud Platform (GCP) Cloud SQL Postgres is an alternative database solution that offers the most similar functionality to API BaaS for JSON blobs and it also has a relational database capability. If you are considering retaining that structure of your data, you should consider this solution.
  • GCP also has a host of other database solutions including Cloud Firestore, Cloud Datastore, Cloud Spanner, and Firebase Cloud Messaging, which provide a range of solutions that go well-beyond the capabilities of Apigee API BaaS.

Customers should determine if one or more such solutions meet their needs.

How do I get my data exported or How do I access the migration tools?

  • For Apigee Public Cloud Customers -- To access the Apigee API BaaS query customer migration tools, log a P3 service request in the Apigee Support Portal (case record type: service request, product: edge cloud, component: API BaaS, subject: BaaS Migration Tool Access) to request access. The export process can take several days or more, depending on the amount of data and other assets that must be exported. The response time will start once you provide the necessary details for Apigee to begin exporting. Please specify if the export is required for testing (quicker export without downtime) or a production cutover. Tools include a migration guide with import instructions, sample code for how to modify your API proxies, and a data export tool. Customers can not use the migration export tool directly. As a result, this must be done internally via a support ticket.
  • For Private Cloud Customers -- Export your API BaaS data using the tools Apigee provides. To get these tools, make sure Apigee API BaaS is on version 17.05.xx or higher and do the following:

    1. Download the rpm using a command such as the following:

      curl https://{username:password}@software.apigee.com/thirdparty/baas/apigee-baas-export-1.0.0-0.0.20002.noarch.rpm -o apigee-baas-export-1.0.0-0.0.20002.noarch.rpm
      
    2. Install the rpm using a command such as the following:

      yum install apigee-baas-export-1.0.0-0.0.20002.noarch.rpm
      
    3. Verify that the export tools have been installed correctly using the details packaged with the software. Under /opt/apigee/apigee-baas-export, you'll find all the required export tool jars and docs with instructions on how to use the export tools.

    4. Follow instructions as given in the doc under the docs directory.

To assist you in your API BaaS migration strategy, design, and implementation, our partners Intelliswift Software and EPAM are available for both Private Cloud and Public Cloud customers. These services are independent of Google and would need to be set up between customers and the consulting companies.

There is also an open source community tool that you can use to get your data into Cloud Firestore.

What will happen if I don't take the necessary actions?

After June 30, 2019, API BaaS will be unavailable to both you and the client applications that use your data there. You will not be able to administer or develop on API BaaS, nor will client applications be able to make calls to your API BaaS services. All data from API BaaS will be deleted after June 30, 2019.

Is Apigee still supporting API BaaS?

Apigee will support API BaaS for both Public Cloud and Edge for Private Cloud 4.18.01 customers until June 30, 2019. Support will be discontinued after June 30, 2019.

What are the options for API BaaS users after June 30th?

To assist you in your API BaaS migration strategy, design, and implementation, our partners Intelliswift Software and EPAM, are available for both Private Cloud and Public Cloud customers. These services are independent of Google and would need to be set up between customers and the consulting companies. Intelliswift plans to provide Intelliswift Usergrid, their hosted version of Apache Usergrid (similar to API BaaS) for customers who wish to stay with a similar solution after the EOL. For more information or to contact these companies, please email Intelliswift at usergrid@intelliswift.com and EPAM at WFBGCPPartnership@epam.com.

Who do I contact if I need more info or help?

To access the Apigee API BaaS query customer migration tools, log a ticket in the Apigee Support Portal (subject: BaaS Migration Tool Access) to request access.

API BaaS migration tools use Node.js code for connecting Apigee Edge to our new database solution. What if I prefer java?

These tools are to assist our customers in migrating to another solution and at the time we determined that Node.js was the best alternative for customers to use. We do not plan to develop a Java equivalent.

Will API BaaS stop working on June 30, 2019?

For Apigee Public Cloud customers, yes. We will not be extending customer support after this date. You will have the option to migrate data to an Intelliswift instance of Usergrid. Please plan to migrate early. These migration services and ongoing support and hosting will be independent of Google and will require you to contract directly with Intelliswift.

For Private Cloud customers, while the product may continue to function, it will not have any updates (including any security patches) going forward. In addition, Apigee Support will no longer assist customers with any issues related to this product.

Are there any tools or support available to redirect API BaaS proxies to new endpoints

Support is not available to handle such requests and we don't have any automated solutions to redirecting endpoints for the proxies.

Is the source code of API BaaS 4.18.01 shared with Private Cloud customers post EOL

No, Apigee will NOT open source 4.18.01 source code or Apigee BaaS portal other than what has already been done as a part of Apache Usergrid.