We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Client/Server Architecture: Past, Present, & Future

77
 Cite
 Share
 Download
 Purchase
No logo availableConfreaks, LLC
 Groseclose, Mike

Formal Metadata

Title
Client/Server Architecture: Past, Present, & Future
Title of Series
Part Number
36
Number of Parts
89
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
The client/server architecture that powers much of the web is evolving. Full stack, monolithic, apps are becoming a thing of the past as new requirements have forced us to think differently about how we build apps. New client/server architectures create a clear separation of concerns between the server and the client. As developers, we have the ability to create the new abstractions that will power the web. Understanding the past, present, and future of the client/server help us to become more active participants in the future ecosystem for building web applications.