The Rest APi

 

The article “What Is a REST API? Examples, Uses, and Challenges”, published on the Postman blog, provides an accessible overview of REST APIs. Rest Api works as a backbone in modern web communication. It explains that a REST API (Representational State Transfer) is a standardized way for systems to exchange data over the web using common HTTP methods such as GET, POST, PUT, and DELETE. It briefly explains the history of the rest api and the comparing to Simple Object Access Protocol (SOAP) api which required strict message formatting and heavier data exchange while REST api emerged as a lighter and more flexible architectural style built on standard HTTP methods. The piece also informs best practices for using REST api like using correct HTTP status codes, providing helpful error messages, enforcing security through HTTPS and tokens, In the end, the article shows real-world examples from well-known platforms like Twitter, Instagram, Amazon S3, and Plaid, showing how REST APIs are used at scale in everyday applications.

As a software developer trying to be a full stack developer, api calls were one of my weakest points since I am struggling to understand how to use it effectively even though I tried to use it in many areas. I had to ensure that I have a strong, up-to-date conceptual foundation of what REST APIs are and how they are designed and used in practice as I use. Since Postman is one of the leading platforms in the API ecosystem, its educational resources provide an excellent reference point for gaining both theoretical and practical understanding of how REST APIs work in real-world development.

Even though the article was long , with YouTube videos and hard time to understand everything, this article with postman helped me to better understand the history and the usage of the rest api and its real-world use compared to before. I learned that REST is not a technology or tool but an architectural style that enforces clear separation between client and server, promotes scalability, and ensures that each request carries all necessary information. Later I plan to use this information to carefully use api as I plan to create my own REST api endpoints that provide access to datasets and user submissions while documenting things well unlike before. Ultimately, my goal is to become comfortable enough with APIs that I can architect entire applications

article link: https://blog.postman.com/rest-api-examples/ 

Comments

Post a Comment

Popular posts from this blog

Is Agile going to fail?

  This article by Jeff Gothelf asks the question “Is Agile finally over?” after 20+ years of implementation to tech field. He argues that even though Agile’s widespread adaptation hasn’t got the result that Agile was intended for. Many companies claimed to be “Agile” as they copy each other, but the implementation of it was shallow or almost non-existent to make changes according to it. Therefore, he says that agile does not seems working as companies try to make employee follow set of rules instead of working in following the basic principles of Agile. He concluded that organizations need to focus on true organizational agility rather than rigid framework adoption. This article caught my attention while searching through the internet as it criticizes Agile’s current status in the business world as ideal of agile does not really fit in reality in organization experience. The vague promises and core ideas are often overlooked to the ‘wants’ of either customer or the organization...
Read more

Waterfall 2.0

  When looking around the internet, I found that there was waterfall 2.0 version of the waterfall software development methodology that we learned at start of class. After I saw the article, I found out that even the most established practices can transform to meet the demands of new era. Therefore, I chose this article as it provides basic summarization of waterfall 2.0 and the difference between traditional waterfall model. As we talked about why waterfall method was being replaced by agile and scrum, I thought there will be some people who will try to improve and use the old working method so using this article showed me how waterfall transformed to adopt need of current workflow. Therefore, I decided to look into it as a background for finding out about the improved version as it revives the dying method into a new form.              This article uses baking as an example to illustrate the principles of waterfall 2...
Read more

Clean code and reality.

  The article examines the question, “is clean code by Robert Martin still matters?” From author’s 16-year coding experience, he writes about reality in writing clean code and its criticism. He acknowledges that t in the end meeting the deadline with functional and bug free code is more important then elegant code following the principle of clean code. However, he argues in the end as a developer, trying to integrate small aspects of clean code into your code base is going to make your skill improve as an engineer in the long run even if many people will not care about it. I selected this article as it addresses some uncertainty that I had with clean code. All the code I have written feels like I got pressure to deliver functional code as quickly as possible and now I’m supposed to write elegant, maintainable code so I wanted to see the real live example from experience if clean code was that necessary. The author’s real-world experience and practical approach toward the subjec...
Read more