To improve performance can follow the below points:
1. Designing the architecture in proper
2. Use design patterns
3. Style of code has to be proper
4. Use pooling mechanism
5. Re factor if any
1.Designing the architecture in proper:
Application (software) architecture
Serves as the blueprint for individual application systems, their interactions, and their relationships to the business processes of the organization.
2. Use design patterns:
a class should have only a single responsibility (i.e. changes to only one part of the software's specification should be able to affect the specification of the class).
Open/closed principle
"software entities … should be open for extension, but closed for modification."
Liskov substitution principle
"objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program."
Interface segregation principle
"many client-specific interfaces are better than one general-purpose interface."
Dependency inversion principle
one should "depend upon abstractions, [not] concretions."
3. Style of code has to be proper:
find out sonar cube problems and rectify the problems, if possible revamp the code and make modularity and as possible as simple.
4.Use pooling mechanism:
5.Re factor if any:
Single responsibility principle
3. Style of code has to be proper:
find out sonar cube problems and rectify the problems, if possible revamp the code and make modularity and as possible as simple.
4.Use pooling mechanism:
5.Re factor if any:
No comments:
Post a Comment