elasticsearch-mapper-attachments VS Spring Boot

Elasticsearch - www.elastic.co/

The increasing complexity of modern systems led to the rise of AIOps (Artificial Intelligence for IT Operations) and observability practices. AIOps leveraged machine learning algorithms to automate problem detection, analysis, and resolution. Observability focused on gaining insights into system behaviour through metrics, logs, and traces. As a result, tools like Prometheus, Grafana, and ELK stack (Elasticsearch, Logstash, Kibana) gained popularity.

My only experience with NetFlow collection is on my home firewall/router running pfSense Community Edition, which is free to download and can be installed on a wide assortment of X86 hardware. I installed the Softflowd package, which exports NetFlow data to a dedicated Elasticsearch/Logstash/Kibana (ELK) server on my LAN. I believe Security Onion and ElastiFlow also can be NetFlow collectors.

Elasticsearch, Logstash, and Kibana (ELK) Stack: An open source suite of tools for log management and analysis, providing real-time insights into security events.

Recently I have taken an interest in big data. https://neo4j.com/ , https://cassandra.apache.org/ , https://clickhouse.com/, https://www.elastic.co/ - are all databases I have experience with. Neo4j and Cassandra only as a hobby, but Clickhouse I have used in production, and Elasticsearch I have used for some 7 years now.

Buy an enterprise-class, wired router like the Negate 2100 ($349 USD), which runs pfSense, and configure the Deco AXE5400 device(s) to operate in Access Point Mode. Then install the Softflowd package through the pfSense web UI. Softflowd will collect and export NetFlow data to a NefFlow collector, which is the separate computer/VM/container referred to above, running software like Security Onion, ElastiFlow, or Elasticsearch/Logstash/Kibana (ELK).

If you’re unaware, elastic search is some like enterprise level search shit. They just put it in a theme. https://www.elastic.co

systemctl status kibana ● kibana.service - Kibana Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2023-03-28 09:40:05 UTC; 33min ago Docs: https://www.elastic.co Main PID: 3168 (node) Tasks: 11 (limit: 9432) Memory: 303.3M CPU: 35.190s CGroup: /system.slice/kibana.service └─3168 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli/dist --logging.dest=/var/log/kibana/kibana.log --pid.file=/run/kibana/kibana.pid "--deprecation.skip_deprecated_settings[0]=logging.dest" Mar 28 09:40:05 wazuh systemd[1]: Started Kibana.

- Usually manually wired and configured vs the spring boot "starter" pattern of having libraries that automatically do some of the manual setup work for you: https://github.com/spring-projects/spring-boot/blob/main/spr...

I wish more client library sets had the feature-matrix that the pulsar one does, because in practice most end up being the same: Java supports everything because it's either built in the same codebase or is the most used client and gets the most support, while the dotnet client codebase has many feature-requests or performance improvement issues, often leading to a "third-party client" being created.

https://github.com/spring-projects/spring-boot/pull/39754/co...

If you’re currently running with an earlier version of Spring Boot, I recommend that you upgrade to Spring Boot 2.7 before migrating to Spring Boot 3.0. It minimizes compatibility issues as much as possible.

Okay, we need to build the game? No problem, we will use Spring Boot and Swing!

It's weird that some people including you directly attack my competence. As a power user you should have plenty of experience getting something to work that is not properly document, does not work how the documentation promised it to, or has weird problems on top of it. Look at idiotic things like this:

https://github.com/spring-projects/spring-boot/issues/33044

Take any similar issue and you'll see a bunch of people who try to find a solution for them because they just aren't repeatable at all. The underlying issue is the auto configuration doing things you can't follow quite properly. It's like it wasn't mean to be understood. Issues like the one I linked above also show me that the spring dev crowd also doesn't understand the ecosystem anymore. The problem is complexity and automagic.

An interested reader can decide for themselves:

https://github.com/spring-projects/spring-boot/tree/main/spr...

Explicitly decoding URL query parameters occurs less often because many frameworks, including Spring Boot, handle decoding automatically.

https://aws.amazon.com/lambda/ https://aws.amazon.com/api-gateway/ https://aws.amazon.com/serverless/sam/ https://aws.amazon.com/cloudformation/ https://aws.amazon.com/s3/ https://spring.io/projects/spring-boot https://start.spring.io