flâneur

Sam Newman - Backends For Frontends

samnewman.io · 3,588 words · saved by 1 readers

With the advent and success of the web, the de facto way of delivering user interfaces has shifted from thick-client applications to interfaces delivered via the web, a trend that has also enabled the growth of SAAS-based solutions in general. The benefits of delivering a user interface over the web were huge - primarily as the cost of releasing new functionality was significantly reduced as the cost of client-side installs was (in most cases) eliminated altogether. This simpler world didn't last long though, as the age of the mobile followed shortly afterwards. Now we had a problem. We had server-side functionality which we wanted to expose both via our desktop web UI, and via one or more mobile UIs. With a system that had initially been developed with a desktop-web UI in mind, we often faced a problem in accommodating these new types of user interface, often as we already had a tight coupling between the desktop web UI and our backed services. A first step in accommodating more than

Sam Newman - Backends For Frontends You are using an outdated browser. Upgrade your browser today or install Google Chrome Frame to better experience this site. Pattern: Backends For Frontends Written on Nov 18 2015 Single-purpose Edge Services for UIs and external parties Introduction The General-Purpose API Gateway Introducing The Backend For Frontend How Many? Handling Multiple Downstream Calls And Reuse For Desktop Web & Other Devices And Autonomy General Perimeter Concerns When To Use Further Reading Conclusion Introduction With the advent and success of the web, the de facto way of deliv

related reading