Apparently JPA Entity have a lifectcycle. See [1].
References
- [1] Baeldung - JPA Entity Lifecycle Events
- https://www.baeldung.com/jpa-entity-lifecycle-events
Apparently JPA Entity have a lifectcycle. See [1].
So, const values must be known at compile time. Hence we cannot use any kind of method to compute const values.
So, are non-const values (which we should take care to make immutable) allowed in a Companion Object? Or is an Companion Object explicitly for constants?
I think it's perfectly safe to use consts and non-consts in a companion object, as long as they're effectively immutable.
Any comments?
The interesting part is that, according to [1], Kotlin inlines the const values where they are actually used. So the definition of the constant has actually disappeared from the compiled byte code. Which is of course much faster, than having to access a constant field somewhere.
Fascinating stuff.
As mentioned in the references below, with some commandline arguments to the JVM, you can force periodic Garbage Collection cycles when on low load to reclaim memory that isn't used (because it's not doing anything).
This comes in handy when using containers, where committed unused memory in the node just costs money.
The application is considered inactive, and G1 triggers a periodic garbage collection if the following conditions hold:
As an example:
This example would indicate that every 30 seconds, if the average system load is below 0.5, a Garbage Collection cycle may be initiated to reclaim memory.
In the past Virtuozzo, which I used, had to put in a java-agent in the command line to have the same functionality. So this is no longer necessary.
Progress!
I had some links to useful websites that I needed to put somewhere.
It seems to be a kind of proxy that you can put between your application and your data layer. It allows for data manipulations, for example using SQL, and your data layer can be anything (and frequently is). If there's an Adapter for it, you can connect Calcite to your data thing. If there isn't you have to write your own adapter.
What it says on the box.
A system to check what your software is doing (in the field).
Find out if there's support for certain frameworks in the GraalVM for Native using this list.
Besides Markdown syntax in JavaDoc in the new versions of Java, it is also possible to add code snippets to your javadoc.
I think it's interesting. It would for example be a good idea to add a code snippet in the JavaDoc that refers to a specific Class in your testset.
There was a talk about hexagonal architecture, that I seem to have seen before.
https://gitlab.com/beyondxscratch/hexagonal-architecture-java-springboot
An interesting little website that can provide REST services about the Star Wars films. If you want to quickly test some REST responses. (Their certificate seems to have expired though)
What is says on the box. Easily selfhosting a cloud environment.
Kind of an standard hosting company, but they seems to have Server Auctions? Buy some cloud with refurbished hardware, is basically the idea. I thought that was interesting.