Backend for Frontend: Tailoring Backend Services for Enhanced Frontend Experience in Telcos

Business strategies today aim to provide a consistent buying experience across all channels. Salesforce Communication Cloud is no exception, serving as a backend application programming interface (API) for various non-native channels.

In an omnichannel interaction, having one common backend API adds to the overhead on the backend APIs and the channels. This overhead arises from large payloads required to support all channels with their data presentation requirements, based on screen types and capabilities. Further, the common backend API becomes challenging to maintain, as it must manage the logic of all channel-specific requirements. This can potentially lead to decreased performance. Therefore, there is a need for separate backends for mobile and web. This requirement has led to the development of the backend for frontend (BFF) pattern, also known as headless architecture.

This paper examines the business challenges that the BFF pattern helps resolve, making it easier for business readers to comprehend and implement. It also discusses the pros and cons of this pattern, enabling technical and business consultants from information technology (IT) teams to make informed recommendations based on specific needs.