Monolithic Architecture

Monolith means composed all in one piece. The Monolithic application describes a single-tiered software application in which different components combined into a single program from a single platform. Components can be:

Authorization — responsible for authorizing a user
Presentation — responsible for handling HTTP requests and responding with either HTML or JSON/XML (for web services APIs).
Business logic — the application’s business logic.
Database layer — data access objects responsible for accessing the database.
Application integration — integration with other services (e.g. via messaging or REST API). Or integration with any other Data sources.
Notification module — responsible for sending email notifications whenever needed.

Example for Monolithic Approach

Consider an example of Ecommerce application, that authorizes customer, takes an order, check products inventory, authorize payment and ships ordered products. This application consists of several components including e-Store User interface for customers (Store web view) along with some backend services to check products inventory, authorize and charge payments and shipping orders.

Image for post — Monolithic Architecture

Despite having different components/modules/services, the application is built and deployed as one Application for all platforms (i.e. desktop, mobile and tablet) using RDBMS as a data source. Benefits and Drawbacks of Monolithic Architecture.

1. Monolithic architecture

2. Layerd archtecture.

3. Virtual machine architecture

4. Exokernel architecture

5. Client server architecture

Micro kernel architecture

Benefits:

Simple to develop — At the beginning of a project it is much easier to go with Monolithic Architecture.
Simple to test. For example, you can implement end-to-end testing by simply launching the application and testing the UI with Selenium.
Simple to deploy. You have to copy the packaged application to a server.
Simple to scale horizontally by running multiple copies behind a load balancer.

Drawbacks:

Maintenance — If Application is too large and complex to understand entirely, it is challenging to make changes fast and correctly.
The size of the application can slow down the start-up time.
You must redeploy the entire application on each update.
Monolithic applications can also be challenging to scale when different modules have conflicting resource requirements.
Reliability — Bug in any module (e.g. memory leak) can potentially bring down the entire process. Moreover, since all instances of the application are identical, that bug impact the availability of the entire application
Regardless of how easy the initial stages may seem, Monolithic applications have difficulty to adopting new and advance technologies. Since changes in languages or frameworks affect an entire application, it requires efforts to thoroughly work with the app details, hence it is costly considering both time and efforts.

Comments

Thread

Thread What is Thread? A thread is a flow of execution through the process code, with its own program counter that keeps track of which instruction to execute next, system registers which hold its current working variables, and a stack which contains the execution history. A thread shares with its peer threads few information like code segment, data segment and open files. When one thread alters a code segment memory item, all other threads see that. A thread is also called a lightweight process . Threads provide a way to improve application performance through parallelism. Threads represent a software approach to improving performance of operating system by reducing the overhead thread is equivalent to a classical process. Each thread belongs to exactly one process and no thread can exist outside a process. Each thread represents a separate flow of control. Threads have been successfully used in implementing network servers and web server. They also provide a suitable foundation ...

Multi Level Queue Scheduling (MLQ)

Multi Level Queue Scheduling (MLQ) · Multilevel queue scheduling classifies the processes according to their types for example, a multilevel queue scheduling algorithm makes a common. · In this scheduling ready queue is divided into various queue that are called sub queues. A subqueue is a distinct operational queue · The process are permanently assigned to subqueues, generally based on some property of the process such as memory size,priority or process type · Each subqueue has its process sucheduling algorithm. For example interactive process at the foreground may use round robin scheduling while batch jobs at the background may use the FCFS method · For example, consider a system with four different queues 1. ...

Multitasking System

Multitasking system · Technically , multitasking is same as multi programming · In a multitasking operating system, s single user can execute multiple programs at the same time · We can also say, multitasking is the system capability to work on more than one job or process at the same time. · It means that whenever a job needs to perform I/O operation, the cpu can be used for execting some other job diagram of multi tasking · There are two type of multitasking : 1. ...

Distributed system

Distributed system · A distributed system is a collection of processor located in geographical dispersal physical location. · In this system, the workhold is distributed or divided between two or more computers that are linked together by communication network . that is the different processors communicate using communication links, such as telephone lines and buses3 · The various processors do not share memory, clock ,or peripheral devices instead each processors has its local memory. · The purpose of distributed system is to provide an efficient and convenient environment for sharing of resources. · Some example of distributed operating system are amoeba, angle, chorus, much, alpha kernel. · ...

Layered Operating System

Layered Operating System Layered Structure is a type of system structure in which the different services of the operating system are split into various layers, where each layer has a specific well-defined task to perform . It was created to improve the pre-existing structures like the Monolithic structure ( UNIX ) and the Simple structure ( MS-DOS ). Example – The Windows NT operating system uses this layered approach as a part of it . Design Analysis : The whole Operating System is separated into several layers ( from 0 to n ) as the diagram shows. Each of the layers must have its own specific function to perform. There are some rules in the implementation of the layers as follows. The outermost layer must be the User Interface layer. The innermost layer must be the Hardware layer. A particular layer can access all the layers present below it but it cannot access the layers present above it. That is layer n-1 can access all the layers from n-2 to 0 but it canno...

Easytolearn

Search This Blog