I have been using gochi/chi router in my go project, and while moving to opentelemetry (OTEL), I noticed that it has weak support for chi router.

Although chi routers are widely used now across highly scalable go applications, but this lack of support causes being dependent on weird (static) scope names, with not much support from otel's own library for golang.

Since the OTEL library is not building new features for such support, I created a new library on the top of OTEL's base project.

Go-chi-otel is an adaption of OTEL go lib, allowing go chi users to now control their traces as they like.

I will be maintaing this project now to support any feature requests, as the library supports instrumentation right now.

You can star the repository if you like to support my initiative :)

I have been working with many clients on different freelance projects, and the one thing that is common in all of them is the security. Most of them need an authentication for their service as well.

In almost all cases, they wanted a simple JWT based authentication for their service. Besides other projects, I never charged much for this one as I had created a boilerplate for authentication with Spring security.

Lately, I decided to opensource a project based on Java and Spring Security, allowing anyone to easily adapt and be able to use for their applications.

I am open for suggestions and positive criticism on the project

I have been interviewing candidates at my company for a while, where we have been asking (experienced) candidates to provide a code-based solution. The idea is to check the code quality.

The candidates, experienced with Java and Spring, end up providing a number of if/else conditions (best they do is a switch case) to switch between strategies, which is completely okay. I felt many aren't aware of Spring Dependency Resolver. This is not an expectation from the candidates, but it felt like many "Spring Boot Experienced" engineers lacked some knowledge about it.

So I have created a sample implementation, which I believe is not redundant, that explains how to use implement Strategy and Factory patterns in Spring boot, that will allow you to just provide a new implementation and Spring will do rest of the magic.

Feel free to share any feedback, I just want to make things easier and better for fellow engineers. And like I said, stars are appreciated if you found it helpful.

I have been interviewing candidates at my company for a while, where we have been asking (experienced) candidates to provide a code-based solution. The idea is to check the code quality.

The candidates, experienced with Java and Spring, end up providing a number of if/else conditions (best they do is a switch case) to switch between strategies. I felt many aren't aware of Spring Dependency Resolver.

So I have created a sample implementation, which I believe is not redundant, that explains how to use implement Strategy and Factory patterns in Spring boot, that will allow you to just provide a new implementation and Spring will do rest of the magic.

Feel free to share any feedback, I just want to make things easier and better for fellow engineers

In this personal case study, I discuss how I improved the performance of my geospatial search queries by leveraging the power of PostgreSQL geospatial indexing. I provide detailed steps on how I optimized my queries, including the use of spatial indexes following the best practices. If you're interested in geospatial data and want to improve the performance of your search queries, be sure to check it out and let me know your thoughts in the comments on the post!

I've created a project that provides in-memory Geo-spatial Indexing, with 2-dimensional K-D Tree. I've worked on multiple projects where I used K-D Trees to find the nearest neighbors for provided geo coordinates with efficient results. I used this implementation for applications with ~35m requests per day, with custom modifications and it worked like a charm. Hence I have created a generic implementation, ready to use. I have already shared great feedback from many programmers and working on improvements already to add new features. The project is open to suggestions and contributions as well. Feel free to create any issues on the GitHub repository.

This is a total aside from someone who doesn't know Java...

But why design Point so that you have to do:

`Point point = new Point.Builder() .latitude(25.2012544) .longitude(55.2569389) .build();`

Instead of:

`Point point = new Point(25.2012544,55.2569389)`

Cool project btw... working with geospatial data can be fun.

builder patterns are very common now because they make maintainability a lot easier, (i.e. if god forbid someone accidentally swapped vars in list of inputsof the same type), and secondly because you can use an annotation library to generate the boilerplate for you, you don't have to write any of it.

Although agreed it's used when you start to get to more parameters. I didn't check but it's possible there are a lot of null/default values like projection or something.

Builder patterns are most useful in statically typed languages that don't have strong support for optional parameters.

In creating a Point, neither value is optional, so I would question the value versus the additional complexity in this case.

Less options for mixing latitude and longitude?

I personally like static methods.

Point point = Point.fromLonLat(55.25…, 25.20…);

The builder pattern is useful to set defaults and add features without breaking backward compatibility.

You can also have cached static instances(assuming immutability), eg Point.fromLonLat(0,0) can always return the same instance, whereas new Point(0,0) must allocate and return a new instance.

> The builder pattern is useful to set defaults and add features without breaking backward compatibility.

Ah, that is interesting. Did not think about that.

thanks - I really wanted a library like this on the JVM

`kdTree.findNearestNeighbor(point, 2);` does this return

1. A list of ALL points that match the distance predicate?

2. Are they sorted by distance to the target?

3. Is it possible to cap to only the closest N points?

I am working on the similar feature Asad You can connect with me on the discord server for geo-assist https://discord.gg/8Xe2Ds4BWj

I would like to have your input and have the better understanding of what you are looking for as well.

now do this in 3d, and forget about the geolocation, move toward establishing location and orientation of limb segments, and establish a set of vectors that will satisfy a required velocity/distance intercept, to coordinate limb function and interaction, then worry about where on the globe, the local instance is with respect to other nearby instances; that would impress me, and would be much more usefull than nearest nieghbours geolocation.