-
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Add Backends For Frontends (BFF) pattern (#300) #3543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
AnveshSrivastava
wants to merge
2
commits into
iluwatar:master
Choose a base branch
from
AnveshSrivastava:backends-for-frontends-pattern
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,148 @@ | ||
| --- | ||
| title: "Backends For Frontends Pattern in Java: Tailoring APIs to Client Needs" | ||
| shortTitle: Backends For Frontends | ||
| description: "Learn the Backends For Frontends (BFF) design pattern in Java. Understand how to give each client type its own dedicated backend service, with real-world examples, code, and diagrams." | ||
| category: Architectural | ||
| language: en | ||
| tag: | ||
| - API design | ||
| - Architecture | ||
| - Client-server | ||
| - Decoupling | ||
| - Microservices | ||
| --- | ||
|
|
||
| ## Also known as | ||
|
|
||
| * Backend For Frontend | ||
| * BFF Pattern | ||
|
|
||
| ## Intent of Backends For Frontends Pattern | ||
|
|
||
| Provide each client-side application (mobile, desktop, chatbot, and so on) with its own dedicated | ||
| backend service, so every client gets an API shaped exactly for its own needs instead of sharing | ||
| one general-purpose backend with every other client. | ||
|
|
||
| ## Detailed Explanation of Backends For Frontends Pattern with Real-World Examples | ||
|
|
||
| Real-world example | ||
|
|
||
| > Imagine a retail company whose mobile app, desktop back-office tool, and support chatbot all | ||
| > need customer, cart, order and supplier data -- but a phone screen wants a short summary while | ||
| > the back-office desktop tool wants full order and stock detail. Rather than exposing one shared | ||
| > API that every client has to filter or over-fetch from, the company stands up a small BFF service | ||
| > for the mobile clients and a separate BFF service for the intranet clients. Each BFF calls only | ||
| > the downstream microservices its client needs and returns a payload shaped for that client. | ||
|
|
||
| In plain words | ||
|
|
||
| > Give every kind of client its own tailor-made backend, instead of forcing all clients through one | ||
| > one-size-fits-all API. | ||
|
|
||
| Sam Newman, who popularized the pattern, says | ||
|
|
||
| > Create separate backend services to be consumed by specific frontend applications or interfaces. | ||
|
|
||
| ## Architecture Diagram | ||
|
|
||
| ``` | ||
| node mobile{ | ||
| component iosapp as "ios app" | ||
| component androidapp as "android app" | ||
| } | ||
| node intranet{ | ||
| component desktop as "desktop app" | ||
| component chatbot | ||
| } | ||
| component bff as "BFF server"{ | ||
| component iosbff as "ios BFF" | ||
| component androidbff as "android BFF" | ||
| component chatbotbff as "chatbot BFF" | ||
| component desktopbff as "desktop BFF" | ||
| } | ||
| node intranetserv as "intranet services server"{ | ||
| component ss as "supplier service API" | ||
| } | ||
| cloud onlypublic as "public cloud"{ | ||
| component cas as "customer authentication service API" | ||
| component cs as "cart service API" | ||
| } | ||
| cloud cloudserv as "managed cloud"{ | ||
| component os as "order service API" | ||
| } | ||
| iosapp -- iosbff | ||
| androidapp -- androidbff | ||
| chatbot -- chatbotbff | ||
| desktop -- desktopbff | ||
| iosbff -- cas | ||
| androidbff -- cas | ||
| iosbff -- cs | ||
| androidbff -- cs | ||
| iosbff -- os | ||
| androidbff -- os | ||
| chatbotbff -- os | ||
| desktopbff -- os | ||
| chatbotbff -- ss | ||
| desktopbff -- ss | ||
| ``` | ||
|
|
||
| This example implements a simplified version of the diagram above with two client-facing BFFs | ||
| instead of four, to keep the demo focused: a **Mobile BFF** standing in for the ios/android BFFs, | ||
| and a **Desktop BFF** standing in for the desktop/chatbot BFFs. Both call into the same shared | ||
| downstream services (`AuthService`, `OrderService`), while `CartService` is only used by the | ||
| Mobile BFF and `SupplierService` is only reachable from the Desktop BFF, matching the fan-out | ||
| shown in the diagram. | ||
|
|
||
| ## Class Diagram | ||
|
|
||
|  | ||
|
|
||
| ## When to Use the Backends For Frontends Pattern in Java | ||
|
|
||
| * Different client types (mobile, web, desktop, voice/chat) need meaningfully different shapes, | ||
| granularity, or aggregation of the same underlying data. | ||
| * A single shared API has grown a large number of client-specific conditional branches, optional | ||
| fields, or query parameters to accommodate every consumer. | ||
| * Different client teams need to iterate on their own API independently without coordinating | ||
| changes through one shared backend team. | ||
| * Some clients (e.g. mobile) need aggressively trimmed payloads for bandwidth/latency reasons, | ||
| while others (e.g. an internal desktop tool) need much richer data. | ||
|
|
||
| ## Benefits and Trade-offs of Backends For Frontends Pattern | ||
|
|
||
| Benefits: | ||
|
|
||
| * Each client gets an API optimized for its own needs, improving performance and simplicity on | ||
| the client side. | ||
| * Client teams can evolve their BFF independently, reducing cross-team coordination. | ||
| * Downstream microservices stay generic and reusable; client-specific logic lives in the BFF | ||
| layer instead of leaking into shared services. | ||
|
|
||
| Trade-offs: | ||
|
|
||
| * Introduces additional services to build, deploy, and operate. | ||
| * Logic that is genuinely shared across clients can end up duplicated across BFFs if not | ||
| carefully factored out. | ||
| * Adds an extra network hop between the client and the downstream services. | ||
|
|
||
| ## How to Implement Backends For Frontends Pattern in Java | ||
|
|
||
| 1. Identify the distinct client types that need meaningfully different data shapes. | ||
| 2. Define the downstream services each client's data actually depends on (`AuthService`, | ||
| `CartService`, `OrderService`, `SupplierService` in this example). | ||
| 3. Create one BFF per client type, implementing a shared `ClientBff<T>` contract, where each BFF | ||
| only depends on the downstream services its client needs. | ||
| 4. Have each BFF aggregate and reshape the downstream data into a response DTO tailored to its | ||
| client (`MobileDashboardResponse`, `DesktopDashboardResponse`). | ||
| 5. Wire the client applications to call their own BFF rather than the downstream services | ||
| directly. | ||
|
|
||
| ## Source Code | ||
|
|
||
| * [Pattern: Backends For Frontends](https://samnewman.io/patterns/architectural/bff/) by Sam Newman | ||
| * [Microservices Patterns: With examples in Java](https://www.amazon.com/Microservices-Patterns-examples-Chris-Richardson/dp/1617294543) by Chris Richardson | ||
|
|
||
| ## References and Credits | ||
|
|
||
| * [Building Microservices](https://www.oreilly.com/library/view/building-microservices-2nd/9781492034018/) by Sam Newman | ||
| * [Pattern: Backend for frontend (microservices.io)](https://microservices.io/patterns/apigateway.html) |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
130 changes: 130 additions & 0 deletions
130
backends-for-frontends/etc/backends-for-frontends.urm.puml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,130 @@ | ||
| @startuml | ||
| package com.iluwatar.bff { | ||
| class App { | ||
| - LOGGER : Logger {static} | ||
| - USER_ID : String {static} | ||
| - PRODUCT_ID : String {static} | ||
| - DEMO_PRICE_USD : double {static} | ||
| - DEMO_STOCK_LEVEL : int {static} | ||
| + App() | ||
| + main(args : String[]) {static} | ||
| } | ||
| } | ||
| package com.iluwatar.bff.bff { | ||
| interface ClientBff<T> { | ||
| + getDashboard(userId : String) : T {abstract} | ||
| } | ||
| class DesktopBff { | ||
| - authService : AuthService | ||
| - orderService : OrderService | ||
| - supplierService : SupplierService | ||
| + DesktopBff(auth : AuthService, orders : OrderService, suppliers : SupplierService) | ||
| + getDashboard(userId : String) : DesktopDashboardResponse | ||
| } | ||
| class MobileBff { | ||
| - MAX_RECENT_ORDERS : int {static} | ||
| - authService : AuthService | ||
| - cartService : CartService | ||
| - orderService : OrderService | ||
| + MobileBff(auth : AuthService, cart : CartService, orders : OrderService) | ||
| + getDashboard(userId : String) : MobileDashboardResponse | ||
| } | ||
| } | ||
| package com.iluwatar.bff.dto { | ||
| class DesktopDashboardResponse { | ||
| - greeting : String | ||
| - loyaltyTier : String | ||
| - orderStatuses : List<String> | ||
| - supplierStockSummaries : List<String> | ||
| + DesktopDashboardResponse(greeting : String, loyaltyTier : String, orderStatuses : List<String>, supplierStockSummaries : List<String>) | ||
| } | ||
| class MobileDashboardResponse { | ||
| - greeting : String | ||
| - cartItemCount : int | ||
| - cartTotalUsd : double | ||
| - recentOrderSummaries : List<String> | ||
| + MobileDashboardResponse(greeting : String, cartItemCount : int, cartTotalUsd : double, recentOrderSummaries : List<String>) | ||
| } | ||
| } | ||
| package com.iluwatar.bff.model { | ||
| class CartItem { | ||
| - product : Product | ||
| - quantity : int | ||
| + CartItem(product : Product, quantity : int) | ||
| + lineTotal() : double | ||
| } | ||
| class Order { | ||
| - id : String | ||
| - productName : String | ||
| - status : String | ||
| + Order(id : String, productName : String, status : String) | ||
| } | ||
| class Product { | ||
| - id : String | ||
| - name : String | ||
| - priceUsd : double | ||
| + Product(id : String, name : String, priceUsd : double) | ||
| } | ||
| class SupplierRecord { | ||
| - productId : String | ||
| - supplierName : String | ||
| - stockLevel : int | ||
| + SupplierRecord(productId : String, supplierName : String, stockLevel : int) | ||
| } | ||
| class User { | ||
| - id : String | ||
| - displayName : String | ||
| - loyaltyTier : String | ||
| + User(id : String, displayName : String, loyaltyTier : String) | ||
| } | ||
| } | ||
| package com.iluwatar.bff.service { | ||
| interface AuthService { | ||
| + getUser(userId : String) : User {abstract} | ||
| } | ||
| interface CartService { | ||
| + getCart(userId : String) : List<CartItem> {abstract} | ||
| } | ||
| interface OrderService { | ||
| + getOrders(userId : String) : List<Order> {abstract} | ||
| } | ||
| interface SupplierService { | ||
| + getSupplierRecords(productId : String) : List<SupplierRecord> {abstract} | ||
| } | ||
| } | ||
| package com.iluwatar.bff.service.impl { | ||
| class InMemoryAuthService { | ||
| - users : Map<String, User> | ||
| + InMemoryAuthService(userData : Map<String, User>) | ||
| + getUser(userId : String) : User | ||
| } | ||
| class InMemoryCartService { | ||
| - cartsByUserId : Map<String, List<CartItem>> | ||
| + InMemoryCartService(carts : Map<String, List<CartItem>>) | ||
| + getCart(userId : String) : List<CartItem> | ||
| } | ||
| class InMemoryOrderService { | ||
| - ordersByUserId : Map<String, List<Order>> | ||
| + InMemoryOrderService(orders : Map<String, List<Order>>) | ||
| + getOrders(userId : String) : List<Order> | ||
| } | ||
| class InMemorySupplierService { | ||
| - recordsByProductId : Map<String, List<SupplierRecord>> | ||
| + InMemorySupplierService(records : Map<String, List<SupplierRecord>>) | ||
| + getSupplierRecords(productId : String) : List<SupplierRecord> | ||
| } | ||
| } | ||
| DesktopBff ..|> ClientBff | ||
| MobileBff ..|> ClientBff | ||
| DesktopBff --> "-authService" AuthService | ||
| DesktopBff --> "-orderService" OrderService | ||
| DesktopBff --> "-supplierService" SupplierService | ||
| MobileBff --> "-authService" AuthService | ||
| MobileBff --> "-cartService" CartService | ||
| MobileBff --> "-orderService" OrderService | ||
| InMemoryAuthService ..|> AuthService | ||
| InMemoryCartService ..|> CartService | ||
| InMemoryOrderService ..|> OrderService | ||
| InMemorySupplierService ..|> SupplierService | ||
| CartItem --> "-product" Product | ||
| @enduml |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <!-- | ||
|
|
||
| This project is licensed under the MIT license. Module model-view-viewmodel is using ZK framework licensed under LGPL (see lgpl-3.0.txt). | ||
|
|
||
| The MIT License | ||
| Copyright © 2014-2022 Ilkka Seppälä | ||
|
|
||
| Permission is hereby granted, free of charge, to any person obtaining a copy | ||
| of this software and associated documentation files (the "Software"), to deal | ||
| in the Software without restriction, including without limitation the rights | ||
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
| copies of the Software, and to permit persons to whom the Software is | ||
| furnished to do so, subject to the following conditions: | ||
|
|
||
| The above copyright notice and this permission notice shall be included in | ||
| all copies or substantial portions of the Software. | ||
|
|
||
| THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
| IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
| FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
| AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
| LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
| OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
| THE SOFTWARE. | ||
|
|
||
| --> | ||
| <project xmlns="http://maven.apache.org/POM/4.0.0" | ||
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
| xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> | ||
| <modelVersion>4.0.0</modelVersion> | ||
| <parent> | ||
| <groupId>com.iluwatar</groupId> | ||
| <artifactId>java-design-patterns</artifactId> | ||
| <version>1.26.0-SNAPSHOT</version> | ||
| </parent> | ||
|
|
||
| <artifactId>backends-for-frontends</artifactId> | ||
|
|
||
| <dependencies> | ||
| <dependency> | ||
| <groupId>org.junit.jupiter</groupId> | ||
| <artifactId>junit-jupiter-engine</artifactId> | ||
| <scope>test</scope> | ||
| </dependency> | ||
| <dependency> | ||
| <groupId>org.slf4j</groupId> | ||
| <artifactId>slf4j-api</artifactId> | ||
| </dependency> | ||
| </dependencies> | ||
|
|
||
| <build> | ||
| <plugins> | ||
| <plugin> | ||
| <groupId>org.apache.maven.plugins</groupId> | ||
| <artifactId>maven-jar-plugin</artifactId> | ||
| <configuration> | ||
| <archive> | ||
| <manifest> | ||
| <mainClass>com.iluwatar.bff.App</mainClass> | ||
| </manifest> | ||
| </archive> | ||
| </configuration> | ||
| </plugin> | ||
| </plugins> | ||
| </build> | ||
| </project> | ||
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No logging instruction in called in the code. You can remove this dependency if not using it.