The Movie Search API is a C# web application that seamlessly connects to the Vimeo online movie database. Leveraging the vast collection of data from Vimeo, this API enables users to search for their favorite movies using specified search terms.

• Vimeo Integration: Utilizes Vimeo's movie database to retrieve detailed information about movies based on user-defined search queries.

• YouTube Integration: Collaborates with YouTube to fetch relevant video URLs associated with the movies found in the Vimeo database. This enriches the user

• Aggregation and Results: Aggregates the information obtained from Vimeo and YouTube, creating a comprehensive set of results. These results include movie details and associated video URLs.

The API I have developed incorporates the use of the Asp.Versioning NuGet package for version control and implementation.

I have organized the implementations into two versions: V1 and V2.

-- V1: Version 1 includes a straightforward implementation of a video aggregator.

-- V2: Version 2, on the other hand, utilizes the Chain of Responsibility pattern for both data aggregation and caching mechanisms, enhancing the overall functionality.

Feel free to explore each version based on your specific requirements and preferences.

├── MovieSearcher
├──src
│   ├── MovieSearcher.Core
│   ├── MovieSearcher.Services
│   ├── MovieSearcher.VimeoWrapper
│   ├── MovieSearcher.YoutubeWrapper
│   └── MovieSearcher.WebAPI
├──test
│   ├── MovieSearcher.Services.Tests
│   ├── MovieSearcher.VimeoWrapper.Tests
│   ├── MovieSearcher.YoutubeWrapper.Tests
│   └── MovieSearcher.WebAPI.Tests.Integration
├── README.md
├── Dockerfile
├── compose.yaml
└── .gitignore

https://github.com/erkinisci/MovieSearcher.git

You have the flexibility to seamlessly configure only Azure App Config using the instructions provided, or alternatively, opt for manual configurations.

Azure APP Configuration

https://learn.microsoft.com/en-us/azure/azure-app-configuration/

• Connections string and label for Azure App Configuration and running standalone app:

"ConnectionStrings": {
    "AzureAppConfig": "*** Use your azure app config connection string"
  },
 "AzureAppConfigLabel": "you label"

• Connections string and label for Azure App Configuration and running docker compose:

"ConnectionStrings": {
    "AzureAppConfig": "*** Use your azure app config connection string"
  },
 "AzureAppConfigLabel": "your label-docker"

Manual Configuration

• Open the appsettings.json file and provide the required API keys in the corresponding sections:

{
  "Vimeo": {
    "AccessToken": "Your Vimeo access token",
    "ClientId": "Your Vimeo client ID",
    "ClientSecret": "Your Vimeo client secret",
    "AppName": "VideoSearch",
    "Search": {
      "Fields": "*** If it is empty, it retrieves all details -but it can also be used as example below",
      "FieldsExample": "name,uri,description,link"
    }
  }
}

{
  "Youtube": {
    "ApiKey": "Your YouTube API key",
    "ApplicationName": "VideoSearchApp",
    "MaxResults": 5
  }
}

"ConnectionStrings": {
    "RedisConnectionString": ""
}

dotnet build
dotnet run

• Retrieves comprehensive details from the API in a paginated manner.

GET http://localhost:${Port}/api/v{version:apiVersion}/movies?query=yourSearchTerm

• Fetches comprehensive details from the API for a specified page.

GET http://localhost:${Port}/api/v{version:apiVersion}/movies?query=yourSearchTerm&page=1

• Retrieves comprehensive details from the API for a specified page, including information about a specified number of videos.

For instance, issuing this request yields details for 100 videos on Page 1.

GET http://localhost:5000/api/v{version:apiVersion}/movies?query=yourSearchTerm&page=1&perPage=100

• The API will internally connect to Vimeo and YouTube, fetch relevant data, and aggregate the results.

• Backend Service Caching The response will be stored in cache database. (2 Hours; default)

• Asp.Net OutputCache - The response will be stored in cache database. (15 seconds; default)

{
  "data":[
    {
      "video":{
        "id":156673345,
        "uri":"/videos/156673345"
        ...
      },
      "videoUrls":[
        "https://vimeo.com/156673345",
        "https://www.youtube.com/watch?v=gVosTabd_1M",
        "https://www.youtube.com/watch?v=vS1UY8KcY30",
        "https://www.youtube.com/watch?v=1NNcTnADt3k",
        "https://www.youtube.com/watch?v=MAX9qWiJx4U",
        "https://www.youtube.com/watch?v=6U4-KZSoe5g"
      ]
    }
  ]
}

• Sets up a local development environment in Docker, including a Redis database.

"ConnectionStrings": {
    "RedisConnectionString": "your-redis-redis:6379"
}

1. Build and Run the Containers:

   Open a terminal in the same directory where docker-compose.yml file and run:

   docker-compose up --build

   This command builds and runs the Docker containers as defined in the docker-compose.yml file.

   docker-compose down

   This command kills the running container

2. Access Your API:

   Once the containers are running, your API should be accessible at http://localhost:8080 in your browser or through any HTTP client.

• Running Main Branch:

  • Builds and runs the containers in Development mode.

• Running Prod Branch:

  • Builds and runs the containers in Build mode.

Vimeo imposes a maximum limit of 100 movies per query, with a default of 25 in the absence of specific query definitions.

  GET /api/v{version:apiVersion}/movies?search=${yourSearchTerm}

  GET /api/v{version:apiVersion}/movies?search=${yourSearchTerm}&page=${pageNumber}

  GET /api/v{version:apiVersion}/movies?search=${yourSearchTerm}&page=${pageNumber}&perPage=${videoCount}

Please note that each request made to the YouTube API through this service incurs a cost of 100 units.

• Quata 10,000 units per day

https://developers.google.com/youtube/v3/guides/quota_and_compliance_audits https://developers.google.com/youtube/v3/determine_quota_cost