sw360 - How new life is been injected in the traditional compliance software
summary
sw360 moves from a 10-year-old Liferay/Cloudant/CouchDB monolith toward modular services: completed work includes a single-step Docker install, unified website documentation, normalized dependency versions and an easier build; ongoing work updates Liferay, rewrites Gradle parts, designs a new authentication framework and a REST API to support a Liferay→SvelteKit front end, and aims to decouple sources as references and consolidate databases (CouchDB/Postgres) — build and deploy are easier but the app remains resource-heavy.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:52SW360 origins and challenges
- 3:36Modernization goals
- 6:06Authentication and DB decoupling
- 8:13Enterprise software evolution challenges
- 9:16Q&A REST API and Docker
- 11:25Development priorities and plans
- 13:38Codebase consistency updates
- 15:43Scalability and testing limits
- 16:47Compliance application integration
- 17:24Data model evolution
- 18:07Open governance collaboration
- 19:10Closing
related talks
25mThe Maintainer’s Perfect Storm: Survival, Succession, and a Decoupled Future
42mThe SBOM Way! The Art of Consuming, Enriching, and Managing Inbound..
39mDoing more with internal developer portals
15mFrom Zero to Hero: Conquering Your DXP with Low Code Kung Fu
20mComposability: The New Architect in Town
48mCombating the struggles of modern cloud-native java developers
33mTools of the Trade
17mDeveloper Experience Q&A