Even though Angular has multiple core technologies which improve with no-effort how our bundle is generated, it's not strange size becomes a problem that require some sort of special caring. In this post we are going to analyze basic tips that ultimately lead to a lighter and snappier Angular application.
One of the key properties for correct pessimistic locking handling and testing is LockTimeout.
Unfortunately its JPA support by different RDBMS providers is far from complete.
In this article I will show you how you may overcome this limitation on Oracle, MySQL, PostgreSQL, Apache Derby and H2.
Moreover, I will give you some suggestions about when pessimistic locking might be the correct solution and when not.
Every now and then your PO (Product Owner), business analyst or project leader will ask you to import an Excel file.
You will decline, he will insist and, in the end, you will give in.
Your data in Elasticsearch is valuable. Therefore the need for backups is provided by the snapshot and restore mechanism in Elasticsearch.
While optimistic locking handling in JPA is relatively well-known, it is usually poorly tested or not tested at all.
In this blog post I will show you firstly what does optimistic locking handling mean and how you could implement it within a Spring Boot Application and JPA.
After that you could see a way to write integration tests, which I hope could surprise you with their simplicity and efficiency!