How recepgunes1/searchengine works
Main Components
• Clients:
• Mobile Application (clients/Mobile) targeting multiple platforms.
• Web Application (clients/Web) serving the browser-based UI.
• Backend Gateway:
• The Gateway service (services/Gateway) that acts as an API aggregator or reverse proxy (using Ocelot configuration files) to route requests to the right microservices.
• Microservices:
• SearchHub, PageDownloader, Summarizer, TagExtractor, UrlExtractor, and UrlRegister.
• Each service is separated into infrastructure (data access, event consumers, extensions, etc.) and WebAPI or Worker projects that implement their business logic.
• Shared Library:
• Under services/Shared, which contains common DTOs, entities, and event definitions that are used across multiple microservices.
• External Systems:
• Databases for various microservices – indicated by deployment YAML files under “deployments/Production/databases”.
• An ElasticSearch instance (see deployments/Production/elastic) used by SearchHub along with possibly other services that reference elastic functionality.
• RabbitMQ (deployments/Production/rabbitmq) for message queuing between services.
Relationships & Interactions
• Clients communicate with the Gateway service that routes the requests to the appropriate microservice. For instance:
• A search request from the mobile or web client is forwarded by the Gateway to SearchHub.
• Other requests (e.g., upload of pages, tag extraction) may be directed to services such as PageDownloader, TagExtractor, or UrlRegister.
• Microservices communicate with shared databases and possibly with each other via messaging queues (as seen with consumer classes and RabbitMQ definitions).
• External API calls (for summarization, for example) are contained in the Summarizer service.
• As a complete system, internal events, DTOs, and messaging are mediated using the shared library.
Key Architectural Patterns
• Microservices architecture: Independent services for different business domains.
• API Gateway: Central point for routing client requests to backend services.
• Distributed messaging: Use of RabbitMQ for communication between services.
• Containerization & orchestration: Dockerfiles, docker-compose, and Kubernetes configuration indicate containerized deployment and orchestration.
• Multi-platform clients: The mobile app supports Android, iOS, Windows, etc., while the web client covers browser interactions.
Relevant Technologies
• .NET (for both backend and mobile/web clients).
• .NET MAUI for mobile application development.
• Blazor/ASP.NET Core (likely) for the web application.
• Docker and Kubernetes for deployment.
• RabbitMQ for messaging.
• Elasticsearch for indexing and search functionality.
• Ocelot for API gateway configuration.
• Shared components:
• External systems:
• For deployment: