In earlier computing models like client-server, the processing load for the application was shared between code on the server and code installed on each client locally. In other words, an application had its own pre-compiled client program which served as its user interface and had to be separately installed on each user's personal computer. An upgrade to the server-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the support cost and decreasing productivity. In addition, both the client and server components of the application were usually tightly bound to a particular computer architecture and operating system and porting them to others was often prohibitively expensive for all but the largest applications (Nowadays,[when?] native apps for mobile devices are also hobbled by some or all of the foregoing issues).[dubious ]
Applications like Gmail started to make their client sides more and more interactive since early 2000s. A web page script is able to contact the server for storing/retrieving data without downloading an entire web page. The practice became known as Ajax in 2005.
"Progressive web apps", the term coined by designer Frances Berriman and Google Chrome engineer Alex Russell in 2015, refers to apps taking advantage of new features supported by modern browsers, which initially run inside a web browser tab but later can run completely offline and can be launched without entering app URL in the browser.
Traditional PC applications consist only of 1 tier, which resides on the client machine, but web applications lend themselves to a multi-tiered approach by nature. Though many variations are possible, the most common structure is the three-tiered application. In its most common form, the three tiers are called presentation, application and storage. A web browser is the first tier (presentation), an engine using some dynamic Web content technology (such as ASP, CGI, ColdFusion, Dart, JSP/Java, Node.js, PHP, Python or Ruby on Rails) is the middle tier (application logic), and a database is the third tier (storage). The web browser sends requests to the middle tier, which services them by making queries and updates against the database and generates a user interface.
For more complex applications, a 3-tier solution may fall short, and it may be beneficial to use an n-tiered approach, where the greatest benefit is breaking the business logic, which resides on the application tier, into a more fine-grained model. Another benefit may be adding an integration tier that separates the data tier from the rest of tiers by providing an easy-to-use interface to access the data. For example, the client data would be accessed by calling a "list_clients()" function instead of making an SQL query directly against the client table on the database. This allows the underlying database to be replaced without making any change to the other tiers.
There are some who view a web application as a two-tier architecture. This can be a "smart" client that performs all the work and queries a "dumb" server, or a "dumb" client that relies on a "smart" server. The client would handle the presentation tier, the server would have the database (storage tier), and the business logic (application tier) would be on one of them or on both. While this increases the scalability of the applications and separates the display and the database, it still doesn't allow for true specialization of layers, so most applications will outgrow this model.
Security breaches on these kinds of applications are a major concern because it can involve both enterprise information and private customer data. Protecting these assets is an important part of any web application and there are some key operational areas that must be included in the development process. This includes processes for authentication, authorization, asset handling, input, and logging and auditing. Building security into the applications from the beginning can be more effective and less disruptive in the long run.
Writing web applications is simplified with the use of web application frameworks. These frameworks facilitate rapid application development by allowing a development team to focus on the parts of their application which are unique to their goals without having to resolve common development issues such as user management. Many of the frameworks in use are open-source software.
In addition, there is potential for the development of applications on Internet operating systems, although currently there are not many viable platforms that fit this model.
- Software as a service (SaaS)
- Mobile development framework
- Web 2.0
- Web engineering
- Web GIS
- Web services
- Web sciences
- Web widget
- "What Is A Web Application?". Stack Path. https://www.stackpath.com/edge-academy/what-is-a-web-application/. "A web application is a computer program that utilizes web browsers and web technology to perform tasks over the Internet."
- Davidson, James Duncan; Coward, Danny (1999-12-17). Java Servlet Specification ("Specification") Version: 2.2 Final Release. Sun Microsystems. pp. 43–46. http://java.sun.com/products/servlet/download.html. Retrieved 2008-07-27.
- Jay Hoffmann (2019-03-04). "What Does AJAX Even Stand For?". https://thehistoryoftheweb.com/what-does-ajax-even-stand-for/.
- Russell, Alex. "Progressive Web Apps: Escaping Tabs Without Losing Our Soul". https://infrequently.org/2015/06/progressive-apps-escaping-tabs-without-losing-our-soul/.
- "Top Tips for Secure App Development". Dell.com. http://content.dell.com/us/en/enterprise/d/large-business/secure-app-development.aspx.
- Multiple (wiki). "Web application framework". Docforge. http://docforge.com/wiki/Web_application_framework.
- HTML5 Draft recommendation, changes to HTML and related APIs to ease authoring of web-based applications.
- Web Applications at Curlie
- Web Applications Working Group at the World Wide Web Consortium (W3C)
- PWAs on Web.dev by Google Developers.
Original source: https://en.wikipedia.org/wiki/Web application. Read more