API Performance Tuning

-
API Performance Tuning

Below are some of the metrics that need to consider while optimizing the performance of APIs/Services:
1) Response Time: Measures how quickly the APIs/Services are responding.
2) Payload and its size: Amount of data transported over the network.
3) Throughput: Number of times the APIs/Services are being invoked.

Some of the techniques which can help to improve those:
Caching
Compression - Compressing the contents before transporting them over the network avoids the latency at the network layer. Compressions like Brotli or GZip can be used to achieve this.
Payload Size - Sending only the needed data to the client reduces the network and other overheads in transporting the data to the client.
Logging - Avoid excessive logging of data to the log files, as this makes the server spend time on logging instead of spending time processing the request.
Optimizing the API/Service Code
To optimize the code at the server level:
- Caching frequently accessed contents on the server.
- Avoiding conversion of contents from one format to another.
- Fetch only the data needed from the database or from any other data source.
- Use connection pooling to connect to DB or any other data sources.
- Eager initialize the contents/objects/details that are needed for the application during the start-up in order to avoid the time spent on the initial requests.
- Avoid/reduce the synchronization area/block within the code.
- Configure proper timeouts to external/third-party calls to avoid thread waits.
Auto-Scaling
Settings
- Connection Pool
- Thread Pool
- Memory and GC
- Cache/Cache framework
- Auto-scaling
- Web server
- Other framework/third-party applications used in the application.

Comments

Post a Comment

Popular posts from this blog

PL/SQL

-
PL/SQL PL/SQL stands for Procedural Language extensions to the Structured Query Language (SQL). PL/SQL can execute a number of queries in one block using single command. One can create a PL/SQL unit such as procedures, functions, packages, triggers, and types, which are stored in the database for reuse by applications. The PL/SQL engine resides in the Oracle engine. The Oracle engine can process not only single SQL statement but also block of many statements. Structure of PL/SQL Block: DECLARE     declaration statements; BEGIN     executable statements EXCEPTIONS     exception handling statements END; / Example : SET SERVEROUTPUT ON; SQL> DECLARE        var varchar2(40) := 'I love GeeksForGeeks' ;      BEGIN        dbms_output.put_line(var);      END;      / PL/SQL Functions PL/SQL functions are reusable blocks of code that can be used to perform specific tasks. They are...
Read more

JAVA8 Features

-
Java8 Features 1) Lambda Expressions : Concise functional code using ->. Lambda Expression basically expresses an instance of the functional interface, Lambda Expression provides a clear and concise way to represent a method of the functional interface using an expression. 2) Functional Interfaces : Single-method interfaces. An interface that contains only one abstract method is known as a functional interface. There is no restriction, that can have n number of default and static methods inside a functional interface. A functional interface is an interface that contains only one abstract method.  @FunctionalInterface annotation is used to ensure that the functional interface can’t have more than one abstract method. Runnable, ActionListener, and Comparable are some of the examples of functional interfaces.   Runnable –> This interface only contains the run() method.   Comparable –> This interface only contains the compareTo() method.   ActionListener –> ...
Read more

Build Automation

-
ANT: Ant was the first build tool released in 2000. Ant was developed on procedural programming idea. Ant was improved with an ability to accept plug-ins and dependency management over the network, with the help on Apache-IVY. Drawbacks: 1) XML is used as a format to write the build scripts. 2) Being hierarchical is not good for procedural programming, and 3) XML is relatively unmanageable.   MAVEN: Maven was introduced in 2004. Maven relied on the conventions and was able to download the dependencies over the network. Benefits : Life cycle of Maven, while following the same life cycle for multiple projects continuously. Problems: 1) Maven does not handle the conflicts between versions of the same library. 2) Complex customised build scripts are difficult to write in Maven, as compared to writing the build scripts in ANT. GRADLE : Gradle came into picture in 2012 Features  Declarative builds and build-by-convention 1) Gradle is available with separate Domain Specific Language ...
Read more