Путевые заметки о знакомстве со Spring Data R2DBC

Привет, Хабр! Меня зовут Каненков Александр, я backend-разработчик в Домклик. Не так давно я резко и с головой погрузился в мир реактивного программирования и очень заинтересовался этой темой. Хочу поделиться кратким введением в Spring Data R2DBC, зачем это нужно, как начать использовать и какие преимущества даёт. Мы разработаем небольшое приложение, добавим flyway и напишем пару тестов.

https://habr.com/ru/companies/domclick/articles/966514/

#java #kotlin #spring_data #r2dbc #testcontainers #flyway

Путевые заметки о знакомстве со Spring Data R2DBC

Привет, Хабр! Меня зовут Александр Каненков, я backend-разработчик в Домклик. Не так давно я с головой погрузился в мир реактивного программирования и очень заинтересовался этой темой. Хочу поделиться...

Хабр

Too many #Spring contexts, Docker containers, and threads? Sergei Chernov explains how context caching really works—and how bad defaults lead to OOMs and flaky tests.

Learn how to control resource usage: https://javapro.io/2025/12/17/optimizing-spring-integration-tests-at-scale/

#SpringBoot #Testcontainers #Java #Frameworks

I've forked JBake, ported to Kotlin, upgraded all deps, added support for Texy!, replaced the backend database, and about to release it to Maven Central within days. Also it's now buildable with Maven, and has E2E tests.
https://github.com/OndraZizka/jbake

#jbake #texy #markdown #freemarker #asciidoc #asciidoctorj #orientdb #neo4j #hsqldb #textile #groovy-templates #gradle #maven #fork #java #kotlin #jade #pug #thymeleaf #testcontainers #static #site #generator #staticsitegenerator

GitHub - OndraZizka/jbake: Java based open source static site/blog generator for developers & designers.

Java based open source static site/blog generator for developers & designers. - OndraZizka/jbake

GitHub

I never expected such an amazing journey when I started working on #testcontainers for #dotnet years ago. I've met many great people and learned a lot. I'm truly grateful for all of it. I never imagined the packages would one day pass 150M+ downloads!

Check out Testcontainers (https://testcontainers.com/) and test against real dependencies with confidence.

Realistic test environments often turn into complex beasts. The TCI framework adds structure and control on top of #Testcontainers—without sacrificing flexibility.
Alexander Bierler explains how.

Read #JAVAPRO now:https://javapro.io/2025/10/10/supercruising-with-testcontainers-making-tests-faster-and-more-flexible/
#CI #DevOps #Java #Frameworks #OpenSource

A new #testcontainers for #dotnet release is available. This release supports .NET 10 and ensures compatibility with Docker Engine v29: https://github.com/testcontainers/testcontainers-dotnet/releases/tag/4.9.0. I'm working on updating Docker.DotNet for full v29 support, so expect a new version soon /cc @docker.

Check out the new available modules like Playwright, Grafana, or my favorite this release, Toxiproxy. It's a really interesting tool for pushing testing further: https://dotnet.testcontainers.org/modules/toxiproxy/.

Release 4.9.0 · testcontainers/testcontainers-dotnet

What's Changed This release adds a new configuration (DOCKER_API_VERSION) that lets you pin and downgrade the Docker Engine API version. This was needed because Docker Engine v29 introduced breakin...

GitHub

Good day folks. How many of you are still battling to repair issues related to testcontainers, java-docker and the Docker 29 release?

#testcontainers #docker #java

If you're updating to #docker engine v29 and using Docker.DotNet, make sure to pin the API version to 1.44 (or similar). v29 breaks the library. More details here: https://github.com/moby/moby/releases/tag/docker-v29.0.0.

I'm working on making Docker.DotNet compatible with v29. An updated version of #testcontainers for #dotnet will be available soon.

A few self-hosters have laughed about the Azure and AWS outages. I think a few of them are now dealing with some outages for tools because #Docker 29.0.0 increased the minimum API version from 1.24 to 1.44, which caused some tools like #Traefik to fail. Their GitHub issue page got quickly flooded with issues. The good thing, people also shared workarounds to get them quickly back on track. I felt sorry for the stress they got in the last days. The Traefik maintainers managed to fix it pretty quickly and shipped 3.6.1, and all is good again.

The question would be, why haven't they seen that one coming? Wasn't it clearly communicated from #Docker, or haven't paid #Traefik maintainers paid enough attention?

The fall-out of that change is quite interesting. It will affect a lot of dependencies like #testcontainers, which have shipped 2.0.2, being compatible with Docker 29.0.0. Seems like some maintainers have some work to do, wish them well.

An important note in the #docker 29.0 release notes is the deprecation of older API versions. Previously Docker was supporting clients going all the way back to v1.12.0 released in 2016. The engine now defaults to requiring v25.0 clients released on 2024-01-19.

Tools that mount the docker socket may need upgrades or workarounds. Breakages have been seen with #watchtower, #portainer, #traefik, and #testcontainers.

https://github.com/moby/moby/pull/51186