📒
Gitoqlok
Gitoqlok
  • 🐱‍👓 Welcome
  • 🟢Changelog
  • ❔FAQ
  • ⚒️Functionality Overview
  • 🐞How to report a bug?
  • 💳License Management
    • Master License key
    • Single License Key
  • Main
    • Git for newbies
    • Collaborative Development with Gitoqlok
    • Gitoqlok Development Set of Rules: Git + Qlik Sense
    • Best Practices to Configure Git Environment
    • How Gitoqlok Bypasses the Git API rate limit
    • How Fast do Git Providers Process Large App Versioning
  • 🏃‍♀️Kick-start
    • Connect Qlik Sense to Git
      • Connect Qlik Sense to GitHub
      • Connect Qlik Sense to GitLab
      • Connect Qlik Sense to Bitbucket
      • Connect Qlik Sense to Azure DevOps
    • Applications Manager: Bulk repository creation
      • From Options Page
      • From Qlik Sense hub
    • Git Settings for repositories
      • Repository grouping
    • Creating Git repository and commits in Qlik Sense
      • Committing Bookmarks to the Git Repository
      • Committing Static Files to the Git Repository
      • Standalone Qlik SaaS Script versioning
      • Committing Qlik Automation to the Git Repository
    • Revert to the previous version of the Qlik Sense application
    • How to Publish an Application?
  • 👩‍💻Tutorials
    • Importing Qlik Apps and App Objects from Git
      • Import
      • Deploy from Git
      • Import Qlik app from existing repository
    • Gitoqlok Helper
      • Time Machine
      • Diff Viewer
      • Set a Thumbnail
      • Sheets Comparator
      • Diff Editor (Merge)
      • Load Script Versioning
      • Highlighted Master Items
      • Tags Manager
      • QVD Links: Data Load Editor
    • Application Checklist
      • Publish checklist to everyone
      • Share checklist privately
    • Environment Migration
      • Export
        • Existing repository
        • Create Repository
        • Download file
      • Import
    • Migration of Bookmarks between Qlik Servers
    • Task Chain
    • Security Rules Manager
    • Dark Theme
    • Collision Detection
    • Business Glossary
    • Usage Management
  • 🤝Third-party Integrations
    • ✨OpenAI
      • AskAI: Sheets and Mesaures
      • AskAI: Documentation Wizard
    • QSDA Pro Integration
      • QSDA Pro Charts Deconstruction
    • Soterre Integration
      • QVD Lineage
      • Global Search
  • Gitoqlok for Power BI
    • Application Checklist
Powered by GitBook
On this page
  • The Challenge of Git Server API Rate Limits
  • Solution

Was this helpful?

  1. Main

How Gitoqlok Bypasses the Git API rate limit

User success story based on how Gitoqlok overcomes a large API request traffic.

The Challenge of Git Server API Rate Limits

Every action that delivers the data from Git repository to a Qlik application triggers a request to the connected Git Server's API. However, as versioned items (applications in our case) grow in size, encompassing numerous sheets, large data files, and user-uploaded attachments, Git Servers enforce rate limits to prevent abuse.

The problem with the limit is caused by the fact that for each individual object in the Qlik application a separate file is created in the repository (for convenience and to avoid conflicts). When receiving data from a repository, the result is the formula 1 file = 1 request to the repository, so for large applications rate limit creates a bottleneck that hampers the smooth versioning workflow.

Each Git Server Gitoqlok integrates with poses variable rate limits. Below you can find a summary table for limits as stated in the documentation:

Git Server Rate Limits:

Git Server
Rate Limit (Requests)
Limit Type
Reference

GitLab

300 per minute

Raw endpoint traffic (for a given project, commit, and file path)

2,000 per minute

Authenticated API traffic (for a given user)

Unlimited; Manual control limits

Self-hosted system: GitLab Enterprise

GitHub

5,000 per hour

Primary rate limit for aythenticated users

15,000 per hour

GitHub Enterprise

BitBucket

5,000 per hour

Access to raw files

1,000 per hour

Access to repository data

Solution

Holistic File Retrieval

Rather than making individual requests for each file, Gitoqlok now downloads a comprehensive repository archive containing all necessary files and intelligently unzips them to extract the required version of a Qlik app. This innovative strategy minimizes the number of API requests, alleviating the risk of encountering rate limit errors from the Git Server.

Users can now confidently commit and update their applications without the fear of disruptions caused by rate limit restrictions. Its holistic file retrieval approach ensures that versioning large Qlik applications remains a seamless and efficient process, promoting a frustration-free experience for users across various Git Servers.

PreviousBest Practices to Configure Git EnvironmentNextHow Fast do Git Providers Process Large App Versioning

Last updated 1 year ago

Was this helpful?

https://docs.gitlab.com/ee/user/gitlab_com/index.html#gitlabcom-specific-rate-limits
https://docs.gitlab.com/ee/user/gitlab_com/index.html#gitlabcom-specific-rate-limits
https://docs.gitlab.com/ee/administration/settings/files_api_rate_limits.html
https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28
https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28
https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/
https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/