From 3717ca9df02a3b39d142de79648ca68bdb1fa791 Mon Sep 17 00:00:00 2001 From: Sam Ferree Date: Mon, 19 Mar 2018 23:36:35 -0400 Subject: [PATCH] fix small typo in Backends for Frontends pattern --- docs/patterns/backends-for-frontends.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/patterns/backends-for-frontends.md b/docs/patterns/backends-for-frontends.md index b07a721b0fa..cc1d73f6755 100644 --- a/docs/patterns/backends-for-frontends.md +++ b/docs/patterns/backends-for-frontends.md @@ -13,7 +13,7 @@ Create separate backend services to be consumed by specific frontend application An application may initially be targeted at a desktop web UI. Typically, a backend service is developed in parallel that provides the features needed for that UI. As the application's user base grows, a mobile application is developed that must interact with the same backend. The backend service becomes a general-purpose backend, serving the requirements of both the desktop and mobile interfaces. -But the capabilities of a mobile device differ significantly from a desktop browser, in terms screen size, performance, and display limitations. As a result, the requirements for a mobile application backend differ from the desktop web UI. +But the capabilities of a mobile device differ significantly from a desktop browser, in terms of screen size, performance, and display limitations. As a result, the requirements for a mobile application backend differ from the desktop web UI. These differences result in competing requirements for the backend. The backend requires regular and significant changes to serve both the desktop web UI and the mobile application. Often, separate interface teams work on each frontend, causing the backend to become a bottleneck in the development process. Conflicting update requirements, and the need to keep the service working for both frontends, can result in spending a lot of effort on a single deployable resource.