The module development and code questions forum is intended to aid those who are developing modules or writing code for Drupal.
Please note that this forum is also not intended for "Is there a module that does..." or "I need help with module x..." questions. It's also not a place to ask developers to write your code for you. Please respect this.
Please do not post general discussions intended to target module developers. If the question you have isn't specifically related to writing a drupal module, please post it in a more appropriate forum.
If you you have drupal installed already and are seeking a module that does a specific task, have a question about a specific module and what it does or if it will fit your use case, please place your questions in the Post installation forum.
If you have a problem or question about a specific module, you should create an issue in the module's issue queue (after checking for an existing issue first).
If you don't have drupal installed yet, please place your questions in the Before you start forum.
I have created an API endpoint in Drupal by configuring a View to fetch audit logs (Drupal 11).
By default, Drupal these APIs do not have built-in rate limiting. In such cases, is rate limiting expected to be configured entirely by the customer and how we can configure these rate limits?
Additionally, is there any documented threshold at which Drupal performance may begin to degrade under high API request volume?
Could you please share any official guidance or best practices regarding rate limiting and performance considerations for Drupal APIs?
Sorry for the subject, but I don't how abstract the subject.
First, I made a mistake: I developed a module called “es_filter_analyser” (with classes, namespace, injection, etc.) and when I uploaded it to Drupal.org, I made a typo and it ended up with the machine_name “es_filter_analyse.”
It took me two months to realize my mistake.
So this morning, I tried to create a new module on drupal.org correctly named “es_filter_analyser,” and I pushed the ISO code to it (modifying the repository in .git/config).
