steve VS Elasticsearch

We use SteVe to centrally manage permitted RFID-tags for a couple of AC chargers and it works well for our use case but it really depends on your needs since OCPP can do much more than that. Some chargers also come with some sort of master-slave functionality so you might not even need external software for what you're trying to achieve.

I am trying to set up SteVe as an OCPP backend to administer a few EV charging points.

You can look at https://github.com/RWTH-i5-IDSG/steve

I use SteVe as my backend for testing. Simple to get running with Docker. https://github.com/RWTH-i5-IDSG/steve

For a fast implementation I would recommend trying one of the many available codes from github (i.e. SteVe, it even comes with a web UI)

I am currently attempting to build a Central System for charging stations. Something like this.

You could check out their GitHub and see what is going on https://github.com/elastic/elasticsearch/issues

Link to GitHub -->

I believe the 1024 limit has been upped in recent versions of Elasticsearch

https://github.com/elastic/elasticsearch/issues/92458

Elasticsearch is written in Java and its source code is available on Github.

I don't think the murmur3 hash implementation has changed since it was added as the default in version 2.0 (see the [changes](https://github.com/elastic/elasticsearch/commits/main/server/src/main/java/org/elasticsearch/cluster/routing/Murmur3HashFunction.java)). The plugin itself has seen [more changes](https://github.com/elastic/elasticsearch/commits/main/plugins/mapper-murmur3) but that's IMO because of internals and not visible changes in the calculations.

Mysql is not as open source as postgres (long story). And you can see how open elasticsearch is by just having access to the bugs database https://github.com/elastic/elasticsearch/issue