To get free Big O cheatsheet, Fill in your name and email to get your copy.
Do not scared, we do not spam your inbox.
If you encounter any problem with download, please reach us via the messanger (Bottom right)
📚 Micro services Architecture and Design patterns.
📚 Data Structures and Algorithm
Download 🔽 Your Free Big O Cheatsheet 🏁 now.
The programmatic way of storing data, so that it can be used efficiently. Almost every enterprise application uses various types of data structures in one or the other way.
Algorithms is a step-by-step e programmatic way of storing data, so that it can be used efficiently. Almost every enterprise application uses various types of data structures in one or the other way.
Every day the complexity of applications are increasing which result in more complex and rich sets of data, due to the complexity we generally face the following 3 types of problems every day.
To solve the above 3 problems (Data Searching, Processor capacity/speed & Too-many requests) we can use the Data Structures.
Data can be organized in a way that data is categorized and sorted before searching, thus allowing us to search instantly.
As we already know the Algorithms is step-by-step procedure for performing an operation. And that operations are used for manipulating the data. Let’s us see the operations or the categories of algorithms.
In the next article in details about the algorithms and the data structures implementation with example.
LIKE | SHARE | FOLLOW
January 08, 2022
Senior Developer | Java & C#.NET | 10++ years of IT experience.
Planning to learn ReactJS or Angular or Flutter.!
Today we will see what are the Saga Design Pattern and types available.
Previously we saw about What is Microservice? and the principles followed while developing MSA and the available design patterns.
The Saga Pattern is a microservices architectural pattern to implement a transaction that extends multiple services.
A saga is a sequence of local transactions. Each service in a saga performs its own transaction and publishes an event. The other services listen to that event and perform the next local transaction. If one transaction fails for some reason, the saga also executes compensating transactions to undo the impact of the preceding transactions.
Consider a Food delivery service flow, When a user places an order, below could be the flow.
December 07, 2021
Senior Developer | Java & C#.NET | 10++ years of IT experience.
Planning to learn ReactJS or Angular or Flutter.!
Today we will see what is the Circuit breaker Design Pattern is.
Previously we saw about What is Microservice? and the principles followed while developing MSA and the available design patterns.
As the name suggests the Circuit breaker design pattern is used to stop the process of request and return with the response if a service is not working.
This design pattern can improve the stability and flexibility of an application.
In a distributed environment, calls to remote services and resources can fail due to transient faults, such as slow network connection, timeouts, or the resource being over-committed or temporarily unavailable. These faults typically fix themselves after a short period of time.
However there can also be situations where faults are due to unforeseen events, that might take longer to fix. These faults vary from partial loss of connectivity to complete failure of a service. In these situations, it might be pointless for an application to keep retrying an operation that is unlikely to succeed, instead, the application should accept that the operation has failed and handled this failure accordingly.
A circuit breaker pattern can prevent an application from repeatedly trying to execute an operation that’s likely to fail. Allowing it to continue without waiting for the fault to be fixed or the utilization of resources does not kill the CPU and memory.
It also enables an application to detect whether the fault has been resolved.
A client should invoke a remote service via a proxy. When the number of consecutive failures crosses a threshold, the circuit breaker trips, and for the duration of a timeout period all attempts to invoke the remote service will fail immediately. After the timeout expires the circuit breaker allows a limited number of test requests to pass through. If those requests succeed the circuit breaker resumes normal operation. Otherwise, if there is a failure the timeout period begins again.
Circuit breaker design pattern
Example:
Consider we have Video Upload and View service when there is a failure in one of the services which triggers the Circuit open and enables the proxy service.
November 30, 2021
Senior Developer | Java & C#.NET | 10++ years of IT experience.
Planning to learn ReactJS or Angular or Flutter.!
Today we will see what is the CQRS – Command query responsibility segregator Design Pattern is.
Previously we saw about What is Microservice? and the principles followed while developing MSA and the available design patterns.
CQRS stands for Command Query responsibility segregator, a design pattern that separates the read and update operations for data.
In traditional architecture, the same data mode is used to query and update the data in a database, This is how the CRUD operations work. With CQRS the read and update operations are separated into two parts, Command and Query.
The command part will handle all the CREATE, UPDATE, DELETE requests, while the Query part will handle all the READ (Materialize view) requests.
Example:
Consider we have Video Services, One for Uploading (Write Operation) and another for viewing (Read Operation).
Where Uploading will perform Create, Update, Delete operations. And the other service on viewing will perform a Select operation to read the videos and their metadata.
November 28, 2021
Senior Developer | Java & C#.NET | 10++ years of IT experience.
Planning to learn ReactJS or Angular or Flutter.!