Differences between Procedural and Oriented Programming Approaches

-

 


Comments

Post a Comment

Popular posts from this blog

C4 model for visualizing software architecture

-
Image
The C4 model was created as a way to help software development teams describe and communicate software architecture, both during up-front design sessions and when retrospectively documenting an existing code base . Although primarily aimed at software architects and developers, the C4 model provides a way for software development teams to efficiently and effectively communicate their software architecture, at different levels of detail, telling different stories to different types of audience, when doing up front design or retrospectively documenting an existing code base The C4 model is an "abstraction-first" approach to diagramming software architecture, based upon abstractions that reflect how software architects and developers think about and build software. The small set of abstractions and diagram types makes the C4 model easy to learn and use Abstractions In order to create these maps of your code, we first need a common set of abstractions to create a ubiquitou...
Read more

Project Effort Estimation Methodologies

-
There are a number of methods that are used for effort estimation. All of them have pros and cons and all depend on the information the effort estimator has, his experience and his judgement.  Below I will explain most of these There are three main approaches for effort estimation: Expert estimation : An expert on the subject of effort gives judgement on this. Formal estimation model: Using a proper model you feed the system with proper data to get some estimation. Combination-based estimation : The estimation arrives with a mixture of both expert estimation and formal estimation procedures. Each approach has one or more methods.  Below you will find the most common ones. Work Break-Down Structure This seems to be the most common method. Using this method you break down the project to the small parts of works, tasks. Then, you estimate the effort for every task. This is an Expert Judgement method and it comes with two flavors:  Three Point System and...
Read more

Sticky Session- Load Balancing

-
Image
Session stickiness , also known as(aka)., session persistence, is a process in which a load balancer creates an affinity between a client and a specific network server for the duration of a session, (i.e., the time a specific IP spends on a website). Using sticky sessions can help improve user experience and optimize network resource usage. With sticky sessions, a load balancer assigns an identifying attribute to a user, typically by issuing a cookie or by tracking their IP details. Then, according to the tracking ID, a load balancer can start routing all of the requests of this user to a specific server for the duration of the session This can prove very helpful, as HTTP/S is a stateless protocol that was not devised with session persistence in mind. Nevertheless, many web applications do have the need to serve personalized user data over the course of a session. Without session persistence, the web application would have to maintain this information across multiple servers, which can...
Read more