For a client in the IT sector, an experienced IT architect with a focus on relational database management systems (RDBMS) is sought to take responsibility for the solution design of a new data-intensive application.
Typical areas of responsibility:
Analysis of existing system landscapes and gathering of functional and technical requirements for data storage.
Design and conception of a scalable, highly available, and secure RDBMS architecture (e.g., based on PostgreSQL, Oracle, or MS SQL Server).
Creation and optimization of data models (physical, logical) and definition of data flows.
Consulting of the development team in the implementation of database structures, stored procedures, and queries.
Planning and support of data migration strategies from legacy systems.
Definition of standards for backup, recovery, and disaster recovery scenarios.
Relevant technologies, tools or methods:
RDBMS: PostgreSQL, Oracle, MS SQL Server, MySQL/MariaDB
Cloud platforms: AWS RDS, Azure SQL, Google Cloud SQL
Modeling tools: ER/Studio, Sparx Enterprise Architect, draw.io
DevOps & IaC: Terraform, Ansible, Jenkins for database deployment automation
Monitoring: Prometheus, Grafana, specialized DB monitoring tools (e.g., pgAdmin, Oracle Enterprise Manager)
Typical KPIs or success metrics:
System availability and uptime (> 99.95%)
Response times of critical database queries (< 200ms)
Adherence to RTO/RPO targets (Recovery Time/Point Objective)
Scalability: performance under load simulation (e.g., 2x user growth)
Reduction of database operating costs through optimized design.
Key challenges, risks or specifics:
Ensuring data consistency and integrity in distributed systems.
Management of schema changes in production (zero-downtime deployment).
Balancing normalization and performance optimization (denormalization).
Securing sensitive data in accordance with GDPR and other compliance requirements.
Concrete deliverables:
Final architecture document (Solution Architecture Document) for the database solution.
Implemented and approved data model.
Proof-of-concept for critical non-functional requirements (e.g., high availability).
Migration plan and test protocols.
Lessons learned / best practices:
Early involvement of development and operations teams is essential.
Automated tests for database schema changes prevent regression errors.
Consider security-by-design from the outset, not as an add-on.