One Article Review
| Source |  AlienVault Lab Blog |
|---|---|
| Identifiant | 8449578 |
| Date de publication | 2024-02-13 11:00:00 (vue: 2024-02-13 14:07:44) |
| Titre | API et automatisation: le bien, le mauvais et le mieux APIs and automation: The good, the bad, and the better |
| Texte | The content of this post is solely the responsibility of the author. AT&T does not adopt or endorse any of the views, positions, or information provided by the author in this article. APIs are often adopted by businesses as a way to automate certain operational tasks. This not only helps to introduce efficiencies, it also reduces the chance of human error in repetitive, manual actions. But the relationship between APIs and automation doesn’t end there. To streamline the API management process, developers have started automating a variety of tasks in the API lifecycle, from development to production. In this article, we explore where these automations live, how they impact the development process, and what teams need to look out for. What is API automation? API automation is the process of automating a variety of tasks associated with designing, building, deploying, testing, and managing APIs. This automated approach lets developers navigate the API lifecycle by using controlled streamlined processes for repetitive, manual tasks. This enables greater consistency throughout the lifecycle, and can improve the success and reliability of functions like testing (both in development and production) and security. In addition, introducing automation also enables more efficiency in the process, allowing developers to focus more of their efforts on more strategic tasks. While not all tasks related to APIs can be automated, there are a variety that lend themselves to it quite nicely. These include: API documentation: Some tools can automatically generate API documentation based on the code base. Code generation: Other tools can automatically create code snippets, using API documentation and specifications as inputs. Versioning: Automated processes can facilitate the management of multiple API versions, ensuring that new changes don’t break anything. Deployment: Introducing automation into the API deployment process can introduce more consistency and reduce the scope of potential errors. |
| Envoyé | Oui |
| Condensat | — and able across actionable actions addition adopt adopted after all allowing almost also analyze any anything api apis applications approach appropriate are around article artificial associated at&t attributes augments author automate automated automatically automatically: automating automation automation: automations bad base based baseline become becoming behaviour being benefits better between beyond both break build building burden business businesses but calls can certain chance changed changes ci/cd classify code collect come common complex conducted confidence consistency consuming content continue controlled core correlate create data defined deploying deployment deployment: designing detect developers development distributing documentation documentation: does doesn’t don’t door down easier efficiencies efficiency efforts element eliminate enable enables end endorse ensure ensuring equips error errors every example executed explore expose external extra facilitate fact fast faster feature feedback flaws focus from functions future gaps generate generation: get gets good greater have help helps how human hundreds identified identify identity immediate impact important importantly improve include: increases increasingly information inputs insights intelligence internal intervals introduce introduced introducing issues it’s key landscape learning lend less lets leverage lifecycle like line live load logic look looking loops lot machine making manage management managing manual many market mile millions monitored monitoring monitoring: more most much multiple navigate need needs new nicely normal not note often one — opt only operational operations other otherwise out outcomes over paced parameters particularly perhaps phase pipeline platform plays positions post potential pre prevent primarily problematic process processes production products programmatically progress prone provided providing push quality quickly quite rate reaching real reduce reduces reducing regardless regularly related relationship reliability remediation repetitive resources responses responsibility right rightfully risk role run runtime saving scope security send sensitive set shortens should simplified simplify snippets solely solution solutions some soon specific specifications spotted standardizes started steps store strategic strategy streamline streamlined success such suite support task tasks team teams test testing tests them themselves there’s these they’re throughout time tool tools transfer useful users using variety versioning: versions views visibility vulnerabilities want way well what where which whole widespread will within words would your |
| Tags | Tool Vulnerability |
| Stories | |
| Notes | ★★★ |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.