API and Modern Day Development

 

 

This article, “Understanding the Role of APIs in Modern Backend Development” starts with what API is and how it is now backbone of modern-day development. APi is a set of rules and protocols that allow software components to interact and expose backend functionality or data to other services, clients, or platforms. The article shows and explain different types of APIs used in backend development, REST APIs, GraphQL APIs, WebSocket APIs. Rest Apis are most used architecture, based on HTTP methods, makint it easy to scale, maintain, and secure. GraphQL APIs are improved alternative of Rest Api, which allows clients to request exactly the data they need in a single query, reducing the number of requests sent to the backend. WebSocket APIs on the other hand, enables bi-directional real-time communication between the client and server making it useful in applications like chat, live updates or gaming. After that the article explains best practices for using API in backend development and they reasons why we need them; Use Clear and Consistent Naming Conventions, Document Your API, Implement Security
This article ends with to popular backend frameworks for building API and why they are used. Examples include Node.js (Express.js), Django (Python), Ruby on Rails (Ruby)  Spring Boot for Java, Laravel for PHP, and FastAPI for Python.

           I recognize that one of the areas I’ve struggled with is using and designing APIs effectively. Therefore, I chose this article, because it tackles that with further knowledge that I currently have. I found out in the world there are more to the Apis than just the Rest Apis and this article well explains other alternatives to Rest Apis and what they do and its examples. Not only that, but the article also explains important things to do while using Apis and popular framework that I can later learn to improve my skills as full stack engineer.

From this article I learned not just new apis and where to use them but also the framework section gave me context about which tools I might adopt based on my need and language, and their benefits. It also expands on what I need to do further implements the practice so I might not be confused in the future while building apis and that they are they are contracts between system. In the future, I will try to better document everything while checking out the version control more carefully than before. Not only that, but I might also try out different Apis to make Backends the other APIs like GraphQL APIs, WebSocket APIs seems useful in parts for future practices. 

 

https://medium.com/@danieltaylor2120/understanding-the-role-of-apis-in-modern-backend-development-36059945db1d 

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