Catatan

Tunjukkan catatan dari April, 2024

The Three-tier Architecture

 An explanation of the three-tier architecture: Imagine a restaurant. The three-tier architecture is like dividing the restaurant's operations into three distinct sections: The Front of House (Presentation Tier): This is where customers interact directly. The waiters (web server) take your order (user request) and deliver it to the kitchen (application tier). The maĆ®tre d' (load balancer) ensures everyone gets seated efficiently, and the security guard (web application firewall) checks for any suspicious activity. The Kitchen (Application Tier): This is the heart of the operation. The chefs (application logic) take your order and prepare the food (process the request) using ingredients (data) from the pantry (database). They might also need to consult a recipe book (business rules) to ensure everything is done correctly. The Pantry (Data Tier): This is where all the ingredients (data) are stored. The pantry manager (database server) ensures everything is organized and r...

Semantic Versioning

 Semantic Versioning  A simple set of rules and requirements that dictate how version numbers are assigned and incremented. These rules are based on but not necessarily limited to pre-existing widespread common practices in use in both closed and open-source software. For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself. Regardless, it is important that this API be clear and precise. Once you identify your public API, you communicate changes to it with specific increments to your version number. Consider a version format of X.Y.Z (Major.Minor.Patch). Bug fixes not affecting the API increment the patch version, backward compatible API additions/changes increment the minor version, and backward incompatible API changes increment the major version. This system is called “Semantic Versioning.” Under this scheme, version numbers and the way they change convey meaning about the underlying code and what h...