>_ BuildaPrompt
TEXT en

Creating a Comprehensive Elasticsearch Search Project with FastAPI

Creating a Comprehensive Elasticsearch Search Project with FastAPI — a ready-to-use text prompt with customizable fields (searchMethod, databaseType, integration) for Development & Code. Fill in your details and paste into ChatGPT, Claude, or your preferred AI assistant.

How to use it

  1. Fill in searchMethod, databaseType, integration below (or keep the suggested defaults).
  2. Copy the generated prompt.
  3. Paste it into ChatGPT, Claude, or your preferred AI assistant.

Pairs well with Ethereum Developer — try running them back to back.

Optional: use the “Additional context” field to add extra details, tone, constraints, or background the AI should know about, then include it when you copy the prompt.

Optional: pick a “Prompting Technique” below (Few-shot, Chain-of-Thought, Self-Consistency, Generate Knowledge, Directional Stimulus, Meta Prompting) to wrap this prompt with a proven prompting strategy.

The base prompt

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} to specify the type of search.
- ${databasetype} for database selection.
- ${integration} to indicate future integration plans.

Want it filled in and enhanced? Use the builder →

Related prompts