2. Read; Web Architecture 🕸️

Web Architecture refers to how a web application is structured and how it’s different components interact with each other to deliver content to users. Here’s a simple explanation:

1. Client-Server Model:

   • Client: The client is usually a web browser (like Chrome, FireFox) or a mobile app. It’s what users interact with. The client sends requests for information, like a web page, to a server.
   • Server: The server is where the website or web application is hosted. It processes request from the client, retrives or generates the requested data, and send it back to the client.

2. Front-End and Back-End:

   • Front-End: This is the part of the appliaction that users see and interact with. It includes the web pages, images, buttons, forms, and other elements. Technologies used here include HTML, CSS, and JavaScript.
   • Back-End: The back-end is the “behind-the-scenes” part of the application logic. It handles data storage, processing, and business logic. Technologies here might include languages like Go, Python, or Java, and databases like PostgreSQL or MySQL.

3. Database:

   • The database stores all the data your application needs such as user information, posts, or products. The back-end communicates with the database to retrive, update, or delete data based on requests form the client.

4. APIs (Application Programming Interface):

   • APIs allow different parts of the web architecture to communicate with each other. For example, the front-end might use an API to request data from the back-end, or the back-end might use an API to get data from an extarnal service (like Payment processing).

5. Layers of Web Architecture:

   • Presentation Layer: This is the front-end that users interact with.
   • Application Layer: This is the back-end where the application logic resides. It processes requests, perform operations, and communicates with the database.
   • Data Leyer: This is the database where all the application data is stored.

6. Web Hosting & Servers:

   • Web applications are hosted on servers, which are computers that run the software and deliver the website to users. These servers can be physical or virtual (Cloud-based).

7. Security:

   • Security is a crucial part of web architecture. It involves protecting the application from theats like hacking, data breaches, and unauthorized access. Techniques include using HTTPS, authentication, and encryption.
     • Data Breaches: A data breach is when unauthorized individuals gain access to sensitive, confidential, or protected data, often leading to the exposure or theft of information such as personal details, financial records, or passwords.

8. Scalability:

   • Scalability refers to the ability of the web application th handle inceasing numbers of users or requests. This can involve adding more servers, optimizing code,or using content delivery networks (CDNs) to speed up content delivery.

   ---

   in short, web architecture is about how allthe pieces-client, server, fron-end, back-end, database, and more - work togather to create a functional and efficient web application that users can access and interact with over the internet.

3. Read; Pros & Cons of ‘Waterfall Development’

The Waterfall development model is a traditional approach to software development where the process is divided into distinct phases, and each phase must be completed before the next one begins. Here are the pros and cons:

Pros of Waterfall Development

1. Simple and Easy to Understand:
   • The Waterfall model is straightforward, with clearly defined stages (e.g., requirements, design, implementation, testing, deployment). This makes it easy for teams to understand and follow.
2. Structured and Organized:
   • Since each phase has specific deliverables and a review process, the Waterfall model is highly structured, ensuring that each stage is fully completed before moving on to the next.
3. Clear Documentation:
   • Extensive documentation is typically created at each phase, providing a clear reference for developers, testers, and stakeholders. This can be beneficial for maintaining and scaling the project later.