elk VS Jetty

Graphviz is the classic option but unfortunately it isn't very good. I mean it was great when it was written in the 80s or whatever but then it seems like it was declared "done" and is still stuck in the 80s.

Quite annoying because it totally dominates the mindshare of graph layout tools, making it difficult to find alternatives.

Here's some other options anyway:

* Eclipse Layout Kernel: https://github.com/eclipse/elk

* OGDF: https://ogdf.uos.de/

In fairness both their websites are pretty terrible (would some examples kill you OGDF?) and they don't provide an easy way to try them out, so I guess it's not that surprising that Graphviz dominates.

Anyway in practice if you have a complex graph then doing it manually is by far the best option.

If it's too big to do manually then it's unlikely to be a useful graph in the first place.

The issue I have with a lot of these tools is they work fine when depicting relationships between tables in the same schema (talking mainly about PostgreSQL databases), but few support showing relationships between tables across different schemas.

Also, when the number of tables grows large, few have layouts arranged in an optimal way. I use D2 (https://d2lang.com/) to create ERDs. However, of the free layout engines available in D2, Dagre (https://github.com/dagrejs/dagre) and ELK (https://github.com/eclipse/elk) both don't have optimal placement of layouts for a sufficiently complicated database.

The session logs show that the application loads configurations and establishes a connection with a PostgreSQL database. This involves initializing a HikariCP connection pool and Flyway for database migrations. The logs confirm that the database schema validation and migration checks were successful. The startup of the Jetty HTTP server follows, and the server becomes operational and ready to accept requests on the specified port.

As described on eclipse.dev/jetty: "Jetty provides a web server and servlet container, additionally providing support for HTTP/2, WebSocket, OSGi, JMX, JNDI, JAAS and many other integrations. These components are open source and are freely available for commercial use and distribution."

Manual instrumentation allows you to define your Spans within the code itself rather than relying on automatic instrumentation finding the entry point for a trace. Manual instrumentation is especially helpful for applications that don’t use an application server such as Tomcat, JBoss, or Jetty.

So, 9.4.48 fixes the first two CVEs, but the last one doesn't mention 9.4 at all, so I'm not sure if that's left out due to EOL status for 9.4.

Fresh off the press: https://github.com/eclipse/jetty.project/issues/8007

If you're doing something pretty simple and need something really lighweight, however, you could go with something like Javalin or even use Jetty directly (the HTTP server which powers Javalin and many other frameworks by default). It's not that hard to do that and that's what I actually would do myself for almost everything... the fewer moving parts you have in your application, the better chances you have of keeping everything up-to-date and the less chance to mess up (with a caveat: bigger frameworks may give you secure defaults that if you're not experienced enough you may not even know about, so it may be better to not go low level if you're new-ish to running web applications securely).

Example: Little Johnny was developing a Java web app and thinking about how he would configure Tomcat to listen to requests and redirect the data into his app... until he remembered this would violate Factor 7! Instead, he decided to declare Jetty as a dependency, keeping the HTTP service inside the app instead of configuring an external web server and then injecting its functionalities. Now, whenever he wants to instantiate another server for this app, all he has to do is installing dependencies and running the app, isn't it convenient?

Hi /r/java! Jetty is considering implementing dynamic Brotli compression, but the current JVM wrapper for Google's Brotli (jvm-brotli) is somewhat ... abandoned.

Multiple applications in the same JVM? Wildfly, Tomcat, Jetty.