Database Architect / Database Engineer

Current State –

• The data stored in this system is for Core payments – partner enablement data and contains partner data platforms like partner records, merchant, token, payment, settlement, and core data.
• This is a horizontal database serving many upstream.
• Today they use Gemfire to store all data, it is a caching tool by VMware and stores data as a key-value pair. Discover stores the data in a structured JSON format in key-value pairs.
• Data is served via APIs
• Gemfire is deployed in 6 regions (multi-regional)

Discover’s migration/re-platform plan

• The long-term plan is to migrate the systems to OCP + Postgres.
• Right now the immediate plan is to move all the data to Postgres by June 2024 as their current Gem Fire license is ending
• The JSON data needs to be moved to Postgress RDBMS structured tables.
• Postgres will be deployed in two regions(east and west), and AWS RDS-managed services will be used.
• Discover plans to use REDIS as the cache
• Updates will be done on Postgres, Read replica will be REDIS
• There are 4 teams (6-8 folks) in Poland, England, and India with different vendors (Cap and CTS) that are doing this activity

JD Profile

• Expert Database Architect with experience in RDBMS Databases (Postgres)
• Experienced in working with AWS RDS, Postgres
• Experienced in migrating databases
• Knowledge of JSON to convert JSON data into meaningful RDBS schemas
• Experienced in designing and building new databases
• Experienced in concepts of partitioning to enable data availability through postgress
• Adequate knowledge in replication, building multiregional databases,  ACID concepts, etc in RDS
• Good to have – knowledge of REDIS cache
• Good to have – Knowledge of GemFire