Request and response flow of multi-tiered architectures

-

Types of N-Tier Architectures

There are different types of N-Tier Architectures, like 3-tier Architecture, 2-Tier Architecture and 1- Tier Architecture.

First, we will see 3-tier Architecture, which is very important.

3-Tier Architecture

By looking at the below diagram, you can easily identify that 3-tier architecture has three different layers.

  • Presentation layer
  • Business Logic layer
  • Database layer






These three layers can be further subdivided into different sub-layers depending on the requirements.

Some of the popular sites who have applied this architecture are

  • MakeMyTrip.com
  • Sales Force enterprise application
  • Indian Railways – IRCTC
  • Amazon.com, etc.

 

Some common terms to remember, so as to understand the concept more clearly.

  • Distributed Network: It is a network architecture, where the components located at network computers coordinate and communicate their actions only by passing messages. It is a collection of multiple systems situated at different nodes but appears to the user as a single system.
    • It provides a single data communication network which can be managed separately by different networks.
    • An example of Distributed Network– where different clients are connected within LAN architecture on one side and on the other side they are connected to high-speed switches along with a rack of servers containing service nodes.
  • Client-Server Architecture: It is an architecture model where the client (one program) requests a service from a server (another program) i.e. It is a request-response service provided over the internet or through an intranet.

    In this model, Client will serve as one set of program/code which executes a set of actions over the network. While Server, on the other hand, is a set of another program, which sends the result sets to the client system as requested.

    • In this, client computer provides an interface to an end user to request a service or a resource from a server and on the other hand server then processes the request and displays the result to the end user.
    • An example of Client-Server Model– an ATM machine. A bank is the server for processing the application within the large customer databases and ATM machine is the client having a user interface with some simple application processing.
  • Platform: In computer science or software industry, a platform is a system on which applications program can run. It consists of a combination of hardware and software that have a built-in instruction for a processors/microprocessors to perform specific operations.
    • In more simple words, the platform is a system or a base where any applications can run and execute to obtain a specific task.
    • An example of Platform – A personal machine loaded with Windows 2000 or Mac OS X as examples of 2 different platforms.
  • Database: It is a collection of information in an organized way so that it can be easily accessed, managed and updated.
    • Examples of Database – MySQL, SQL Server, and Oracle Database are some common Db’s.


Comments

Post a Comment

Popular posts from this blog

Spark Cluster

-
Image
Spark applications run as independent sets of processes on a cluster, coordinated by the   SparkContext   object in your main program (called the   driver program ). Specifically, to run on a cluster, the SparkContext can connect to several types of  cluster managers  (either Spark’s own standalone cluster manager, Mesos or YARN), which allocate resources across applications. Once connected, Spark acquires  executors  on nodes in the cluster, which are processes that run computations and store data for your application. Next, it sends your application code (defined by JAR or Python files passed to SparkContext) to the executors. Finally, SparkContext sends  tasks  to the executors to run. There are several useful things to note about this architecture: Each application gets its own executor processes, which stay up for the duration of the whole application and run tasks in multiple threads. This has the benefit of isolating applications from ...
Read more

DORA Metrics

-
 DORA metrics, often referred to as the DORA (DevOps Research and Assessment) metrics, are a set of key performance indicators (KPIs) used to measure and assess the effectiveness of an organization's DevOps practices. DORA metrics were developed by the DevOps Research and Assessment team, which includes notable figures in the DevOps community such as Dr. Nicole Forsgren and Jez Humble. The DORA metrics encompass four key areas: 1. **Deployment Frequency:** This metric measures how often an organization deploys code changes to production. Higher deployment frequencies indicate a more agile and responsive development process. 2. **Lead Time for Changes:** This metric tracks the time it takes for code changes to go from code commit to being deployed in production. Shorter lead times suggest efficient and streamlined development and delivery processes. 3. **Mean Time to Recover (MTTR):** MTTR measures how quickly an organization can recover from failures or incidents in production. Low...
Read more