I'm looking forward to seeing my local app works without Docker installed but with TestContainers Cloud + Kafka remotely and so on. This is awesome! :)
Hi guys, great job. I would love to have a library like this to use as automation for local environment projects. Now that Docker is paid, my company is migrating to podman, just for local environment, and it's a little tricky to switch from Docker, most developers are having issues with it, I think it can be a great solution for that.
@@tcharl an autoservice would work for non-jdbc containers, like MongoDB or Kafka, and it can provide a better integration with the rest of the framework, for example with the DevTools not to restart the containers on DevTools reload. tc:// works because it matches the jdbc driver provided by Testcontainers which will manage the lifecycle of the containers for you. @Testcontainers is a JUnit integration to manage the containers lifecycle along side of the unit tests lifecycle. One lifecycle management mechanism is enough that's why tc worked. PS. Sorry for the longest ever response time, my past attempts at commenting somehow are not displayed. (Oleg)
![[VDBUH2024] - Josh Long - Bootiful Spring Boot 3.x](http://i.ytimg.com/vi/3SiYK0BWr0M/mqdefault.jpg)
This is a fantastic demo. Always love the energy Josh Long brings to any session. He is full of enthusiasm. THanks for sharing this.
Amazing demo! Sometimes I think Josh talks telepathically with his IntelliJ. He’s that fast during Demos!
I'm looking forward to seeing my local app works without Docker installed but with TestContainers Cloud + Kafka remotely and so on. This is awesome! :)
This is absolutely awesome. Thanks for the demo and all the hard work behind it.
ofc we all love Josh
Amazing guys, thanks for all..
Thanks, great video!
Thanks guys! Quite interesting demo (:
Awesome stuff!!
Hi guys, great job. I would love to have a library like this to use as automation for local environment projects. Now that Docker is paid, my company is migrating to podman, just for local environment, and it's a little tricky to switch from Docker, most developers are having issues with it, I think it can be a great solution for that.
Amazing
Cool 👍
Hi, do we need docker should be installed in our pc?
I'm going to publish this into my own project. Has anyone done another iteration of auto-services with dev-tools?
Does anyone know how to get Testcontainers up and running with Gradle & Kotlin?
How do we mix testcontainers, mysql & flyway?
What's the point of the experimental autoservice if the magic "tc://" url works on runtime. Sorry but didn't get it.
And the corollary: why tc:// worked without the @TestContainer annotation :-)
@@tcharl an autoservice would work for non-jdbc containers, like MongoDB or Kafka, and it can provide a better integration with the rest of the framework, for example with the DevTools not to restart the containers on DevTools reload.
tc:// works because it matches the jdbc driver provided by Testcontainers which will manage the lifecycle of the containers for you. @Testcontainers is a JUnit integration to manage the containers lifecycle along side of the unit tests lifecycle. One lifecycle management mechanism is enough that's why tc worked.
PS. Sorry for the longest ever response time, my past attempts at commenting somehow are not displayed. (Oleg)
sounds painful for m1 developers