Skip to main content

AccelByte Cloud 3.0.0

Last updated on

AccelByte Cloud 3.0.0​

AccelByte 3.0.0 also known as AccelByte 2.42.0 before. There is API Gateway Removal, so we decide to bump up the major version of AccelByte.

This doc only provides the highlight of the release. Please follow the AccelByte 3.0.0 Bi-weekly Release Report for detailed information on what's changed, the version of each service, and the deployment changes to upgrade to the latest AccelByte.

There are a number of updates in this version that we hope you will like, some of the key highlights include:

API Gateway Removal​

API Gateway is a layer at the top of our backend services that aims to be an entry point of all HTTP requests. Moreover, API Gateway has some extended logic that we built to achieve some requirements, such as session management, legal management, IP Geolocation, filter user profile information, rate limiter, and device information.

After having the AccelByte API Gateway for more than a year, we found several relatively high-impact issues, especially regarding our AccelByte product's reliability and resilience. Furthermore, we need to re-evaluate API Gateway usage since we have some infrastructure changes.

After some evaluation, currently, we are removing API Gateway. There will be several behavior changes in the Session Management feature, IAM, Legal, and all of AccelByte Services including Customer Repository. There also some adjustments for Frontend and SDK.

Friend Notification: Unfriend, Cancel or Reject Friend Previously, Lobby hasn't sent a notification for some interaction in friend feature so for the current implementation in the game make more server calls to friend feature that make some heavy server traffic. Also, as a Player, you might want to get notified when someone unfriend, cancels, or reject you as a friend.

Currently, we are adding some Notifications in the Friend Feature, so you can be notified when someone unfriend, cancels, or reject you as a friend.

In-App Purchase Update (Backend)​

As a player want to be able to purchase a virtual currency through 3rd party Store so that they can use it to buy in-game items. However, there are some issues related to this that we need to handle to make the sync process working as expected.

So, we are updating the platform service to Handle packageType Null for PSN, Handle empty config. Backend will still send a blanks response when you get it and there will be an error when sending a request to 3rd Party Platform.

  • Remove DOCUMENT_TAG table and include tag as field in BASE_POLICY table

    Previously, the tag is represented as a record in DOCUMENT_TAG table which only consists the value of the tag. This is actually unnecessarily and we can simplify it by adding new field on BASE_POLICY table that include multiple tag.

  • Improve Eligibility Checking. For endpoint /public/eligibilities/namespaces/{namespace}/countries/{countryCode}/clients/{clientId}/users/{userId} we are decreasing the query used by hibernate and rely on the local cache.

  • Remove AFFECTED_CLIENT table and include affected client as field in BASE_POLICY table. Previously, affected_client is represents as record in AFFECTED_CLIENT table which only consist the value of the clientId.

This is actually unnecessarily and we can simplify it by adding new field on BASE_POLICY table that include multiple clientId.

Bug Fixes and Feature Enhancement Highlight​

  • Fix: Get linked platforms failed if legal is not accepted yet
  • Fix: Cannot see the key of Product Keys from the Purchased items
  • Fix: After Getting a Chat Ban User Still be Able to Send a Message
  • Fix: DS Image isn't deleted in the ECR
  • Fix: Presence data is truncated when Game Client set the presence status