Monolithic architecture

In today’s world, the debate is still going on about which architecture suits best in every perspective. We will discuss in a shorter context about this topic.

Monolithic is a coupled, single-packed architecture that combines all the services related to the business under a single shed. It includes all related services such as web server, load balancer, database, UI/UX, business layer, and interfaces. It integrated everything into a single-piece server as a product.

Examples of such organizations such as Facebook, GitHub, Epic System, and WordPress.




We will see the pros and cons of using monolithic architecture.

Benefits

Easy deployment: Since monolith is a single unit, it is easy to deploy.

No coupling time: There is no run-time and design-time coupling between multiple components.

Operations: Operations that take place locally and can be done in ACID (Atomicity, Consistency, Isolation, and Durability) implementations since it uses a single database.

Performance: Due to a single repository, one API is sufficient to perform all the functions.

Drawbacks

Slower deployment: As the name says, if any small changes are made in a single part of the architecture, the entire architecture should be changed accordingly.

Time-consumption: It’s a time-consuming process due to modifying takes a lot of time.

Redeployment: It’s not an easy task to restructure the entire architecture.

Complex structure: A monolithic application takes a longer time to develop and it is more complex and slower.

Reliability: The entire system will be affected if one module gets any error and stops the product.

Maintenance: It costs high maintenance due to the single components which contain all subdomains.

Still, it has many advantages and disadvantages,75% of the companies are using monolithic architecture. Architecture has been decided to structure based on the requirement. So, it plays a crucial role when you want to build perfect software.

 

Comments

Post a Comment

Popular posts from this blog

How to Install Jenkins

Image
Jenkins is an open-source Java application server for Continuous Integration and Continuous Delivery (CI/CD). This will run in servlet containers such as Apache Tomcat. It helps the developers to build, test, and deploy the software by automating using CI/CD pipelines. It detects bugs and notifies the developers in an early stage. How to Download and Install: Step 1: Go to https://www.jenkins.io/ . Click Download Step 2: Download Jenkins ‘Generic Java package’. I prefer to download the LTS package (It is a stable one). Step 3: Select your desired path after downloading and save the Jenkins.war file in your local system. Step 4: Go to command prompt (Windows) | Terminal (IOS)                Go to the folder where the war file is saved. Then, type the command java -jar Jenkins.war and run it. It will take a while to run the command. It gives an admin password. Note it down to use Jenkins the first time. The ...
Read more

HTTP Payloads

Image
 What happens when I send a letter without information to the receiver that I require some details from them? What happens when the receiver writes a response to my letter without having the information I need? This information is similar to the body generally called a payload in HTTP request and response.  Let us see the payload in the HTTP request and HTTP response individually. I have added the below image to explain the HTTP request and response body/payload in JSON. I have used BurpSuite to take this image and Swagger Petstore (petstore.swagger.io) for this example. HTTP Request Payload Generally, the payload is not required for all the requests and responses. GET and HEAD methods usually do not require a body while sending a request to the server. The above example is a POST request to create a resource name 'doggie'. To achieve this, I should send some information about the resource which is called HTTP request payload. Breakdown of request payload: Content-Type:  ...
Read more

Embedded testing - Introduction (Part 1)

 I'm writing a series about my recent learnings in embedded testing. Here is the basic introduction about this topic with a simple example. Scenario 1: A patient books an online appointment to provide a blood sample for a hemoglobin level test. To book an appointment, the patient only needs access to a web or mobile application. When a quality engineer tests the functionality of this appointment registration process, it is referred to as software testing. Scenario 2: The patient now wants to collect the test report after the blood sample analysis. To measure the hemoglobin level, the lab technician uses an automated medical device. At this stage, if the quality engineer is involved in testing, they require both a physical device (hardware) to process the sample and an application (software) to enter or capture the details. When testing involves both hardware and software, it is referred to as embedded testing. Click here to read the next blog
Read more