Path traversal

 














Comments

Post a Comment

Popular posts from this blog

Abstraction and Encapsulation

Image
Encapsulation is the act of protecting data integrity.  A class is properly encapsulated when its internal data cannot possibly be set to an invalid or inconsistent state.  This can be achieved by: 1) Information hiding: removes the class's internals from the eyes of its clients so that there is less risk of corrupting of corrupting those internals. 2) Bundling of data and operations: helps establish a single entry point for all actions to be done on this class.  This way you can perform all required validation and integrity checks before modifying this class. Each class has a number of invariants, these are conditions that must be true at all times. It is the responsibility of the software developer that these invariants are never violated and the best way to do that is to encapsulate your classes so that this is never an option. Example: the set method of the invariants are marked as private so only the class may set it.  In this a course cannot be active if the nu...
Read more

Microservices and Service-Oriented Architecture

  Microservices Architecture and Service-Oriented Architecture (SOA) , along with their similarities, differences, and typical use cases. Microservices Architecture Microservices is an architectural style where applications are composed of small, independent services that communicate over a network. Each service is typically designed around a specific business function and operates as an isolated, self-contained unit. Here are some key characteristics: Independently Deployable : Each service can be developed, deployed, and scaled independently of others. Single Responsibility : Services are organized around business capabilities, such as “Order Processing” or “User Authentication.” Resilience : Each microservice operates independently, making the system more resilient since failures in one service do not necessarily impact others. Polyglot Persistence and Programming : Microservices allow for diverse technologies, frameworks, and databases across services, optimizing each service...
Read more

Version control and Continuous Integration/Continuous Deployment (CI/CD)

 Version control and Continuous Integration/Continuous Deployment (CI/CD) are fundamental practices in modern software development that enhance collaboration, maintainability, and quality of software projects. Below, we’ll explore each concept, including their principles, benefits, and key practices. Version Control Version Control is a system that records changes to files or sets of files over time, allowing developers to track and manage changes to their codebase. It facilitates collaboration among team members and provides a history of changes, making it easier to revert to previous versions if needed. Key Principles of Version Control Track Changes : Every change made to the codebase is recorded, allowing developers to see who made changes, what changes were made, and when. Branching and Merging : Developers can create branches to work on features or fixes in isolation without affecting the main codebase (usually referred to as the main or master branch). Once the work is co...
Read more