Types of Algorithms

A list of algorithm approaches you can use to solve many problems.

Brute Force

Also referred to as exhaustive search because it is a naive approach that looks at all possible solutions for the problem and chooses the best solution.

Divide and Conquer

There are two components to this algorithm. The first step is to determine if you can split your current problem into smaller sub-problems and then combine smaller sub-problems to find the answer.

Decrease and Conquer

This approach is used when you only have one sub-problem, but you can filter the input by a simpler function in order to decrease the amount of complexity of the problem.

Greedy Approach

This algorithm is used to find the approximate best answer for hard problems. What it does is at a given time, it will take the locally optimal choice with the intent for finding the optimal solution.

Dynamic Programming

Another approach of splitting up a complex problem into overlapping sub-problems, using the answer for the sub-problems to answer the initial problem. This usually involves saving the answer to certain sub-problems to be used later.

Backtracking

Backtracking algorithms can be used when you are finding all answers that satisfy a certain constraint. It will build its solution as long as it satisfies the condition, and throw it out once it does not.

Comments

Post a Comment

Popular posts from this blog

Uncle Bob's Clean Architecture

Image
The basis of my current understanding of architecture comes from the brilliant mind of Robert C. Martin (Uncle Bob). You can find the original post through his blog , which I strongly encourage you to read. In this post I'll try to summarize some of the key points I've understood from his post. Clean Architecture Source Clean architecture is a design used to emphasize the structure and relation of your various code components to promote the idea of Dependency Rule , such that "source code dependencies only point inwards" . Clean architecture is able to promote this by defining that your software system consists of various layers , that can be organized in such a way that the layers point in one direction, and a dependency graph will not have circular reference. The reason this is important is because it allows you to keep closely code related, and increase clarity of how components fit into your system. Explaining the Layers We can really separate out this ...
Read more

RabbitMQ: A Look into Messaging Queues

RabbitMQ and Messaging Queues Messaging queues plays a large role in the communication channels of large enterprise systems. A message queue/broker is an added system that stores a queue of messages between multiple systems.  Message queues will bring general consistency to your architecture by providing a delivery mechanism that ensures the proper delivery of your messages. To integrate message queues into your architecture, we're going to have to re-think how we connect our services together. RabbitMQ is a popular framework for implementing message queues within your system, although there are alternatives such as SQS or MSMQ. Components Messaging Queues consists of three main components. Publisher - This is a system that emits some message within your environment. The message is then stored to the message queue. The Message Queue - A system that stores the messages in a queue to be consumed by other systems in your environment. Consumer - A system that takes ...
Read more

Template WebAPI: One Solution Structure to Rule Them All

A part of the Template WebAPI series. Solution Structure The first distinction that I want to make about the project is the solution structure and how to organize your code. As of the the date of this post, the package structure is as so: project src clients template.Api core template.Domain template.Application template.Persistence test project This folder is used to store any project assets that may need to be edited by the developer, such as ignore files or deployment files (such as docker). Files that generally don't get touched by developers can stay outside of the solution. src This folder contains all of the code used to execute the running application(s). clients Clients are the executable running projects that combine integrate the software into a single application that will be used by consumers. There may be many clients, such as support systems such as cache services, running jobs, or other systems that support your main application. ...
Read more