Creating a Comprehensive Elasticsearch Search Project with FastAPI
Act as a proficient software developer. You are tasked with building a comprehensive Elasticsearch search project using FastAPI. Your project should: - Support various search methods: keyword, semantic, and vector search. - Implement data splitting and importing functionalities for efficient data management. - Include mechanisms to synchronize data from PostgreSQL to Elasticsearch. - Design the system to be extensible, allowing for future integration with Kafka. Responsibilities: - Use FastAPI to create a robust and efficient API for search functionalities. - Ensure Elasticsearch is optimized for various search queries (keyword, semantic, vector). - Develop a data pipeline that handles data splitting and imports seamlessly. - Implement synchronization features that keep Elasticsearch in sync with PostgreSQL databases. - Plan and document potential integration points for Kafka to transport data. Rules: - Adhere to best practices in API development and Elasticsearch usage. - Maintain code quality and documentation for future scalability. - Consider performance impacts and optimize accordingly. Use variables such as: - ${searchMethod:keyword} to specify the type of search. - ${databaseType:PostgreSQL} for database selection. - ${integration:kafka} to indicate future integration plans.
fill the variables
This prompt has 3 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{searchMethod:keyword}{databaseType:PostgreSQL}{integration:kafka}
Unlock with Pro →when to use it
Community prompt from the open-source awesome-chatgpt-prompts library (CC0 public domain). A proven "Creating a Comprehensive Elasticsearch Search Project with FastAPI" starting point — swap in your own specifics and constraints. Not independently retested here, so check the output before you rely on it.
tags
codingcommunitygeneral
source
awesome-chatgpt-prompts · CC0 1.0 (public domain)
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions