DNA One
Enterprise Backend Engineering & Platform Enhancement
A technical case study describing backend feature development, platform enhancement, security improvements, automation, gateway development, and dependency modernization delivered for the DNA One client project.
1. Executive Summary
DNA One is an enterprise platform supporting applications and workflows related to DNA analysis and laboratory operations. The platform uses a modern Java/Spring backend, PostgreSQL data layer, Angular frontend, and messaging infrastructure to support application workflows.
As a Backend Engineer, I contributed to enhancing the platform through end-to-end backend feature implementation, API development, scheduled data-management processes, external gateway development, security improvements, dependency upgrades, and search/filter functionality.
The work covered both new feature development and modernization of existing components, with a focus on reliability, security, maintainability, and predictable sprint delivery.
2. Project Overview
2.1 Project Objective
- Implement and enhance backend capabilities required by the application.
- Provide APIs and business logic consumed by the frontend.
- Automate data backup and sample lifecycle operations.
- Provide a controlled integration point for external vendors.
- Improve security by resolving CodeQL findings and vulnerable transitive dependencies.
- Improve search and filtering capabilities.
- Deliver assigned work using an Agile, sprint-based model.
2.2 Role & Focus
- Backend API implementation and enhancement
- Business-logic development and database interaction
- Cron Job implementation for automated data operations
- External gateway and security implementation
- Dependency analysis, upgrades, and vulnerability remediation
- Search and filter predicate implementation
- Backend testing, issue resolution, and sprint delivery
3. Technology Stack
| Layer | Technology |
|---|---|
| Programming Language | Java 25 |
| Backend Framework | Spring Boot 4 |
| Application Framework | Spring Framework 7 |
| ORM | Hibernate 7 |
| Application Server | Tomcat 11 |
| Database | PostgreSQL 18 |
| Frontend | Angular 20.3.16 |
| Runtime | Node.js 22.12.0 |
| Build Tool | Apache Maven 3.9 |
| Messaging | ActiveMQ 6.1.5 |
The stack combines a modern Java/Spring backend with PostgreSQL, Angular, Node.js tooling, and ActiveMQ messaging to support enterprise application development, API integration, persistence, scheduled processing, and asynchronous communication.
4. Role & Responsibilities
5. Key Technical Contributions
5.1 Backend API Implementation
Implemented backend APIs required to populate data in the frontend application and support end-to-end feature workflows.
- Designed and implemented REST endpoints adhering to enterprise standards.
- Developed required backend business logic and service layers.
- Integrated API processing seamlessly with the PostgreSQL database layer.
- Handled request/response serialization, validation, and defensive error propagation.
- Supported smooth frontend-to-backend data flow for lab technicians and operators.
5.2 One-Time Data Backup Using Cron Job
Built a scheduled Cron Job to perform a one-time backup of required data with verifiable execution integrity.
- Implemented scheduled Cron execution triggers with boundary conditions.
- Added logic to accurately identify and filter targeted backup datasets.
- Executed atomic backup operations safely through managed backend threads.
- Added controlled execution, retry policies, and detailed failure-audit handling.
5.3 Automated Sample Deletion
Implemented backend functionality for automatic sample deletion through scheduled processing as well as an action-handler based deletion flow.
- Implemented regulatory sample-deletion business logic and compliance checks.
- Added Cron Job based automatic purge execution on defined retention cycles.
- Implemented action-handler based deletion for explicit operator-triggered flows.
- Ensured all deletion operations strictly followed defined application data-retention criteria.
5.4 External Gateway as a Service
Developed an External Gateway service to provide a controlled integration point for external vendors. The gateway operates as a reverse proxy between external consumers and internal backend services.
| Capability | Contribution |
|---|---|
| Reverse Proxy | Forwarded external requests to appropriate internal backend services without exposing internal network topology. |
| Authentication | Applied authentication controls before allowing access to protected internal services. |
| Authorization | Controlled role-based access and scoped resource authorization for external endpoints. |
| Asymmetric Cryptography | Worked with asymmetric-cryptography requirements (public/private key signing) for secure external integration. |
| Gateway Service | Provided a dedicated, auditable service boundary separating external vendor traffic from core cluster resources. |
5.5 Search & Filter Predicate Logic
Implemented backend logic to dynamically construct search predicates for searchable columns and filter predicates for filterable columns.
- Converted arbitrary frontend search criteria into secure, parameterized backend query conditions.
- Built dynamic JPA/Hibernate predicates based on user-selected columns and operators.
- Supported multiple simultaneous searchable and filterable columns with compound AND/OR logic.
- Integrated predicate construction with PostgreSQL database query execution plans for sub-second retrieval.
5.6 Dependency Upgrade & CodeQL Remediation
Worked on resolving CodeQL findings and vulnerabilities originating from transitive dependencies across Maven builds.
- Analysed static application security findings flagged by GitHub CodeQL scans.
- Identified affected direct and transitive third-party dependencies in the POM tree.
- Upgraded libraries to hardened, secure versions compatible with Java 25 & Spring Boot 4.
- Validated regression compatibility through integration test suites.
- Reduced security posture exposure and supply-chain maintenance risks across the organization.
6. Security & Dependency Modernization
Security and maintainability were key parts of the backend engineering work, covering both application-level security requirements and dependency-level vulnerability remediation.
6.1 External Integration Security
- External gateway used as a controlled entry point for vendors.
- Authentication and authorization applied to protected routes.
- Reverse-proxy architecture separated external access from internal services.
- Asymmetric cryptography requirements were incorporated into the external integration design.
6.2 Code Security
- CodeQL findings were analysed and addressed systematically.
- Vulnerable transitive dependencies were identified and upgraded.
- Dependency changes were validated to eliminate regression risk.
- Security improvements were incorporated into normal sprint development activities.
7. Agile Development & Delivery
Development was carried out using an Agile methodology with sprint-based planning, implementation, testing, review, and delivery.
| Practice | Application |
|---|---|
| Sprint Planning | Work was broken down into manageable, sprint-level development user stories and technical tasks. |
| Incremental Delivery | Features and backend improvements were delivered in manageable increments verified in staging. |
| Collaboration | Worked with project stakeholders, product owners, and engineering teams during implementation. |
| Testing | Backend changes were validated through rigorous development, unit-level, and integration testing activities. |
| Code Quality | Security findings and dependency issues were addressed alongside feature work in continuous integration. |
| No Spillover | Assigned sprint commitments were delivered without carrying unfinished work into subsequent sprints. |
8. Technical Architecture & End-to-End Flow
The backend work followed a layered request-processing model in which frontend requests are received by backend APIs, processed through business logic and security controls, and persisted or retrieved through the database layer.
| Layer | Responsibility |
|---|---|
| Angular Frontend | User-facing application and data presentation (Angular 20.3.16). |
| Backend REST APIs | Request handling, validation, and API contract definition in Spring Boot 4. |
| Business Logic | Validation, search/filter predicates, actions, and laboratory workflows. |
| PostgreSQL | Persistent application data, relational transactions, and indexed genomics records. |
| Scheduled / Integration Services | Cron Jobs, external gateway reverse proxy, and ActiveMQ messaging-related processing. |
8.1 Representative Data Flow
- 1
Frontend API Request
Frontend requests data through a backend REST API with required parameters and authentication tokens.
- 2
Request Validation & Auth
The backend validates and processes the request through Spring filters and security interceptors.
- 3
Dynamic Predicate Application
Business logic applies dynamic search/filter predicates, access controls, or feature workflows.
- 4
PostgreSQL Database Interaction
The backend interacts with PostgreSQL via Hibernate 7 ORM as required for reads, transactions, or mutations.
- 5
Response Delivery to Frontend
The processed response DTO is serialized and returned to the Angular frontend for rendering.
- 6
Scheduled Asynchronous Operations
Scheduled jobs execute controlled background backup routines or automatic sample-deletion workflows independently.
- 7
External Gateway Verification
External vendor requests enter through the External Gateway with asymmetric-crypto checks before reaching protected internal services.
9. Key Technical Highlights
Backend Engineering
- Java 25 and Spring Boot 4 backend development
- REST API implementation and enhancement
- Business-logic development and validation
- PostgreSQL data access and query-related processing
- Dynamic search and filter predicate construction
Automation
- Cron Job implementation and scheduled thread execution
- One-time data backup automation
- Automatic sample deletion on lifecycle expiration
- Action-handler based deletion workflows
Security & Integration
- External Gateway reverse-proxy service
- Authentication and authorization gateway boundaries
- Asymmetric cryptography signing for vendors
- CodeQL issue remediation
- Transitive dependency vulnerability upgrades
Engineering Practices
- Agile sprint-based methodology
- Sprint-based incremental delivery
- Backend testing and unit/integration validation
- Proactive dependency and supply-chain management
- No Spillover delivery track record
10. Conclusion
The DNA One project provided hands-on experience in enterprise backend engineering using the modern Java and Spring ecosystem. As a Backend Engineer, I contributed across API development, business logic, database operations, automation, external integrations, security, and dependency modernization.
The combination of feature development and platform-level improvements provided exposure to production-oriented engineering concerns such as secure external access, automated data lifecycle management, dependency vulnerabilities, dynamic query construction, and predictable Agile delivery.
The work strengthened my ability to design and implement backend capabilities that integrate with frontend applications, databases, scheduled processes, and external systems while maintaining focus on security, reliability, maintainability, and sprint commitments.
Need Regulated Backend Engineering for Your Team?
Explore how our engineers build, secure, and modernize Java & Spring systems with predictable sprint delivery.