Delve into software architecture, exploring key principles, patterns, and quality attributes. Gain insights with case studies and projects, enhancing your practical skills in system design and optimization.

Software Architecture in Applications-01.png

This course offers a deep dive into the world of software architecture. It’s designed to equip software developers and architects with the knowledge and skills necessary to create, evaluate, and optimize software systems. The course covers a range of critical topics to ensure a strong foundation in architectural principles and strategies.

You will start by exploring architectural concepts and the relationship between quality attributes, requirements, and architectural styles. You’ll also examine different architectural patterns and strategies, including centralized and decentralized architecture, layered pattern, broker pattern, and microservices. Then, you’ll go into the details of important quality attributes needed while developing an architecture.

The course is equipped with multiple case studies and two projects to further enhance learning. These real-world scenarios and hands-on projects are strategically incorporated to give learners practical insights.

Software Architecture in Applications

# Overview

**Client-server architecture** is a two-layered, and typically two-tiered, architecture. Therefore, this architecture can be considered a C&C architecture type as well. The client-server architecture is a distributed program in which clients and servers communicate directly with one another. A client requests a resource or uses a service provided by a server, and the server answers the client's requests. A single server can have several clients connecting to it.


# Where is business logic located?

The client component of the program includes the user interface code in this design, whereas the server part contains the database. Both the server and the client contain the business logic. The majority of the application's business logic is saved on the server, although it may be stored on the client as well. The application logic of the server may reside in software components, the database, or both.


The client is said to be a full-featured client when it comprises the majority of the business logic. If most of the functionality resides on the server, the client is referred to as a thin client, which is preferable. A thin client makes deployment easier.

In most circumstances, the application logic is distributed across the client and the server. If consistency isn't used, it might be difficult to always know where a certain piece of logic is situated. If we're not cautious, business logic on both the client and server sides might be duplicated.
 
In some cases, the same piece of logic might be required on both the client and server sides. For example, the user interface might need business logic to validate a piece of data before submitting it to the server. The server might require the same logic, because it must, likewise, execute this validation. While centralizing this function might need an extra connection between the client and server, the alternative (duplication) reduces maintainability, because if the business logic changes, we must modify it in numerous locations.

Learn about the client-server model and its pros and cons.

Getting Started

The Architecture Meta-Frame

Architectural Styles and Strategies

Architectural Styles and Strategies

Scalability

Availability

Load Balancing

A Basic Load Balancer

Security

Caching

Web Architecture

Case Studies

A Basic MVC Data Flow

Conclusion

Client Server

Overview

Where is business logic located?