Search for the Holy Grail (and test it once found)
summary
A distribution web app (the download server/Bintray style) uses Grails + MongoDB + Elasticsearch: Grails for the UI and REST API, MongoDB for schema‑free metadata, and Elasticsearch on a separate search server so search doesn’t consume app JVM CPU/memory. Indexing happens automatically from GORM events via the elasticsearch plugin. Team reports fast feature rollout, acceptable performance, and no relational DB pain. Testing strategy favors Spock tests for integration-style specs plus JUnit/TestNG data‑driven unit tests.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:15About JFrog and Grails
- 8:13Web app requirements
- 13:43Simple app demo
- 16:19Search types and needs
- 21:15Search solutions overview
- 23:04Lucene and Compass in Grails
- 27:49Solr and Elasticsearch issues
- 31:35Elasticsearch history
- 35:36Elasticsearch in Grails
- 39:44Testing options in Grails
- 40:06JUnit and data tests
- 43:49TestNG benefits
- 45:39Spock testing framework
- 49:15Grails in IntelliJ IDEA
- 51:04Grails and MongoDB experience
related talks
01h 30mThe Quest for the Holy Grails
01h 08mGrails Plugin Testing Strategies
50mTesting Java Code Effectively
01h 32mTesting Grails
49mInside the Elastic: Testing a Well Known Open Source Stack
49mFabulous Tests with Spock and Groovy
49mTesting a Large GraphQL API With Aplomb
20mBrowsers need not apply, UI testing with Lustre and Gleam