https://provokedynamic.tech/posts/Recent content in Posts on ProvokeDynamic | Giorgi ChapidzeHugo -- gohugo.ioen-usWed, 14 Jan 2026 00:00:00 +0000https://provokedynamic.tech/posts/datasource-proxy/Wed, 14 Jan 2026 00:00:00 +0000https://provokedynamic.tech/posts/datasource-proxy/Why Use a DataSource Proxy? The Hibernate user guide recommends using a DataSource proxy instead of default logging frameworks like Log4j or Logback. While traditional logging frameworks can show you SQL statements, a DataSource proxy gives you much more insight into what’s happening at the JDBC level. Benefits of using a DataSource proxy: Statement execution time - See how long each query takes, making performance issues easier to spot JDBC batching logs - Verify that batch operations are actually being batched, not executed one by one Database connection monitoring - Track connection acquisition and release patterns N+1 query detection - Assert the expected number of queries in tests, catching performance problems early Traditional logging frameworks like Logback can be configured via spring-logback.https://provokedynamic.tech/posts/nginx/Mon, 05 Jan 2026 00:00:00 +0000https://provokedynamic.tech/posts/nginx/Nginx is a fast, efficient web server that handles lots of concurrent connections without eating your RAM. It’s used for serving sites, routing traffic, and load balancing. Root vs Alias root - Adds the request path to your root directory: location /admin/ { root /var/www/locked; } Request for /admin/secret.html looks at /var/www/locked/admin/secret.html. Notice it kept the /admin/ part. alias - Replaces the matched location: location /admin/ { alias /var/www/locked/; } Same request now looks at /var/www/locked/secret.