Implement a Postgres driver for GoTick to support distributed scheduling with Postgres as the backend storage
🚀 Problem Solved
Currently, GoTick lacks support for persistent storage solutions, limiting its scalability and fault tolerance in distributed environments. By implementing a Postgres driver, GoTick can utilize a robust and widely-used relational database to manage job states and configurations, allowing for persistent and reliable scheduling across distributed systems
💡 Proposed Solution
Develop a Postgres driver that adheres to GoTick’s storage interface. The driver should include methods for connecting to a Postgres database, reading and writing job states, handling cluster configurations, and ensuring data consistency
🔄 Alternatives Considered
Alternatives include using other databases like MySQL or NoSQL solutions such as MongoDB
🔥 Feature Description
Implement a Postgres driver for GoTick to support distributed scheduling with Postgres as the backend storage
🚀 Problem Solved
Currently, GoTick lacks support for persistent storage solutions, limiting its scalability and fault tolerance in distributed environments. By implementing a Postgres driver, GoTick can utilize a robust and widely-used relational database to manage job states and configurations, allowing for persistent and reliable scheduling across distributed systems
💡 Proposed Solution
Develop a Postgres driver that adheres to GoTick’s storage interface. The driver should include methods for connecting to a Postgres database, reading and writing job states, handling cluster configurations, and ensuring data consistency
🔄 Alternatives Considered
Alternatives include using other databases like MySQL or NoSQL solutions such as MongoDB
📦 Additional Context
No response
📚 Related Issues
No response