This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

BackEnd for Front End (BFF) vs API Gateway - where do they fit in Apigee World

Posted on 10-02-2024 05:12 AM
aakashsharmaa5
Bronze 5
Bronze 5
Reply posted on --/--/---- --:-- AM

Hi All,

Recently, we came up with a requirement where we have to expose the API(s) for multiple channels e.g web and mobile. These can be considered as experience API(s).

A common discussion for this requirement on web is centered around 2 patterns BFF and API Gateway. API Gateway pattern is mentioned as single point of failure where as BFF is an extension of API Gateway catering to different clients/channels and tailoring the response as per their needs e.g different aggregation or fields. Refer to link-https://alirezafarokhi.medium.com/bff-pattern-vs-gateway-pattern-45706ffb9978

I wanted to know to what extent the limitations of API Gateway are applicable to Apigee (single point of failure, seperation of concerns etc.). Can we implement BFF in Apigee as it's a mature APIM platform or via configurations/topology. Also, what are the approaches being followed for BFF Implementation on GCP such as Move aggregation Logic to Micro Service/Nano service in GKE and keep Apigee proxy light weight with pass throughs or Security only. Any inputs are welcome. 

aakashsharmaa5_0-1727870129001.png

aakashsharmaa5_1-1727870517144.png

@feigal Posting here for deeper discussion 🙂

thanks,

Aakash

1 2 2,140
2 REPLIES 2