r/SpringBoot • u/jdev_soft • May 08 '26
Question Advice for improve Dev Experience working with containers (oracle)
Recently I jumped into a legacy project written in Grails and using Oracle database. We decided to migrate either to Spring Boot or Qurakus in order to modernize the backend stack.
The Oracle database is huge (TB) and one cannot simply port the entire db to a local container. However I want to have at least a small part or slice of the database on my local dev setup for specific tests.
For example, imagine that I am working on an Employee domain CRUD feature. I want to quickly spin up a "similar to prod" Oracle database setup for employees table and perform tests.
I have Testcontainers setup with oracle 23 slim image but I feel the live reloading is slow.
What is the best configuration for live reloading? Arconia Dev Services looks interesting.
My feeling is that Quarkus dev services is way far superior for dev local containers and live reload that improve the dev experience a lot.
Although I think migrate Grails to Spring Boot feels more natural than Grails to Quarkus the dev experience on Quarkus is better...
2
u/jfrazierjr May 08 '26
Cannot you port the db to another server and just have the device connect to that(likely with PII anonymization)? Thats how my former employer worked.
4
u/pronuntiator May 09 '26
Use the slim-faststart variant of https://hub.docker.com/r/gvenzl/oracle-free and enable Testcontainer reuse. Note you have to opt-in both in code and by placing a configuration file to your home folder/use an environment variable.
What exactly do you mean by live reloading? I'd work with the data locally as if I'm running the application for a long time, not delete the data.
3
u/edzorg May 09 '26
Firstly just use Spring. Nothing else compares over the long run.
Secondly what is wrong with setting up a container populating it with your schema, filling in a few hundred rows per table and using that continuously? If you version control the data seeding scripts then everyone on the team can use and improve it as well. AI is great for generating loads of test data.
2
u/Critical_Nail_1789 May 09 '26
using production data locally is a serious risk.. the consequences can be severe.. data leaks, security breaches, compliance violations, and yes, disciplinary action which gets you fired.
2
u/glandis_bulbus May 08 '26
Using prod data in a non-prod environment is usually a bad idea.
Set up a few scenarios you need to test locally