The KipSQL database project requires an SQL layer that includes a user interface, parser, optimizer, and executor. The parser must include semantic analysis to validate the legality of the abstract syntax tree. The optimizer must quickly find the most efficient query execution plan based on the cost model. The executor must execute the physical plan by sending read and write requests to the underlying kv storage. Future research includes processing a table to key-value mapping relationship and implementing a push-based execution vector execution model similar to DUCKDB.