AuthZed’s Post

What is an API? Visual explanation of how it works. 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐀𝐏𝐈? APIs are mechanisms that enable two software components to communicate with each other using a set of definitions and protocols. 𝐇𝐨𝐰 𝐝𝐨𝐞𝐬 𝐢𝐭 𝐰𝐨𝐫𝐤? The application sending the request is called the client, and the application sending the response is called the server. In the honey bee example, the hive is the client, the flower is the server, and the bee is the way to communicate (REST API request). 𝐓𝐲𝐩𝐞𝐬 𝐨𝐟 𝐀𝐏𝐈𝐬? - SOAP APIs (Simple Object Protocol uses XML) - RPC APIs (Remote Procedure Calls) - Websocket APIs (used JSON) - REST APIs (uses HTTP, most popular and flexible) Image credit: Rapid_API

LOG SOCKET API CLIENT by Myskill client socket API logs: * log: (logging) the process of recording activities that occur in our application   - aims to find out what errors might occur when the program runs   - errors occur due to the runtime environment, incorrect program logic or bugs in the applications we create   - various logs: error warning log, info log, debug log, trace log   -logrus is a structured logger from Golang fully compatible with the standard library logger API * socket: in the socket there are 3 data communications, namely:   - simplex: data communication that does not allow the receiver and sender to exchange information   - half duplex: data communication between two sending and receiving parties sharing information interactively but not at the same time   - full duplex: data communication between both parties can share information and communicate interactively at the same time * API client: a library that helps your application make a large number of requests on a large scale, an example of this is Heimdall   - the goal is as a means of communicating our application with external parties

📣A set of helper libraries for Minimal API projects. A great feature is the Source Generator for automatically registering endpoints: 1: Implement auto-generated IEndpointRouteHandlerBuilder interface 2: Call the MapEndpoints() method in the Program.cs https://hubs.li/Q02qJlT-0

Customizing the QueryInterface and GetIids methods.

Initializing APIs manually when doing syscalls is painful. At lease a dozen NT APIs have to be initialized, let alone others that have to be obtained through PEB walking. This little demo uses pointer to step through the struct of NT APIs and arrays of names to initialize them in a loop. Reduce code amount to less than 1/3. Though still have to update several places (API, the name string for debug, the hash), but I have put them all in "apisets.c/h" files. No need to jump around and manually write each init now. Btw, don't have to worry about the string array, that's for debug purpose only. I separated them so I can always strip them when in release mode, no trails left behind. Update Makefile variables and you're good to go. Hope this helps a bit. Code here: https://lnkd.in/gh-MaKve

npm install <package_name>, pretty easy to just install a package and use it, but ever wondered how one is made? Well, let me tell you, compiling a package is not as easy as importing one is. I was free last Saturday morning, and was wondering what should i bless my GitHub with. And then came the idea of what could be a better idea than to convert my first piece of code to a package or maybe a Microservice (frontend-based), and then I just let the magic flow on VS Code and created the 'Reaction Time Microservice'. Made a Test Area, where the person can give the "Reaction Time Test" in the first iteration and then moved on to converting it to a microservice. Used 'recharts' to convert all the data fetched from the tests into proper charts for a better view of how a person performed and how decently a person is progressing. The graph shows "Overall Reaction Time History", "Average of all Tests", and "The Recent Best Results" (this was inspired by Monkeytype[i love it]). The microservice/library has been deployed on npm and has about 200+ downloads (noob stuff after all). interested in trying it out? just do a: npm i @goyalsamarth/reaction-time-microservice link to the npm package: https://lnkd.in/gNFuuMN3 link to the GitHub repo: https://lnkd.in/gyG-mKhp

Adding to my Rest API Part 2 is an example of how to use a Rest API. https://lnkd.in/gnfbWMuM

Simple API query program that lets you check IP reputation.

How kubectl exec works: 1) First it looks kubeconfig file for connect to master Node $HOME/.kube/ ( you can see while executing kubectl with verbose mode: -v=8) and makes a tcp connection Master Node with POST request. (debug log) I0907 14:39:13.298881  9252 loader.go:372] Config loaded from file: $HOME/.kube/config 2) Api-server receives this POST request and gets - Pod Execution Options, Node Information and exec URL for a pod container. 3) It connects to Kubelet port which runs on Worker Node and serves an api over a port for api-server requests. 4) Kubelet computes a response endpoint for exec requests. kubelet implements RuntimeServiceClient interface which is part of Container Runtime Interface.It just uses gRPC to call a method through Container Runtime Interface (which is calls RuntimeServiceServer on the Container Runtime side). 5) After Kubelets invoke method on Container Runtime side, it executes exec command on the Worker Node to target container through Kernel. You can check all the details with code examples and points: https://lnkd.in/ezF78u2q Thanks for great post Erkan Erol!

Discover my verified achievement on Make! 🚀The "API Calls with HTTP Modules" course in Make Advanced delves into the art of making requests and handling responses with APIs using HTTP modules. You'll learn to interact efficiently with web services, manipulate data, and automate workflows. Benefits include a thorough understanding of APIs, seamless integration of external services, and optimization of development processes.