MUGOYA DIHFAHSIH

A RESTful API is an application program interface ( API ) that uses HTTP requests to GET, PUT, POST and DELETE data. A RESTful API -- also referred to as a RESTful web service or REST API -- is based on representational state transfer ( REST ) technology, an architectural style and approach to communications often used in  web services  development. REST technology is generally preferred to the more robust Simple Object Access Protocol (SOAP) technology because REST leverages less   bandwidth , making it more suitable for internet usage. An API for a website is   code   that allows two software programs to communicate with each another . The API spells out the proper way for a developer to write a program requesting services from an operating system or other application. This video by Kevin Babcock details RESTful API design and related HTTP concepts. The REST used by browsers can be thought of as the language of the internet. With cloud use on the rise, APIs are emergin

This article aims to give a  solid  explanation of SOLID Principles and give some insight on their benefits and potential issues when applying them. Let’s go through each of them briefly. S — Single Responsibility Principle(S.R.P) A class should have one, and only one, reason to change. When requirements change, this implies that the code has to undergo some reconstruction, meaning that the classes have to be modified. The more responsibilities a class has, the more change requests it will get, and the harder those changes will be to implement. The responsibilities of a class are coupled to each-other, as changes in one of the responsibilities may result in additional changes in order for the other responsibilities to be handled properly by that class. What is a responsibility?! A responsibility can be defined as a reason for change. Whenever we think that some part of our code is potentially a responsibility, we should consider separating it from the class. Let’s say we

What You Should Know About Continuous Deployment Software DevOps emerged as the result of companies’ desire to shorten the software development lifecycle. The goal behind DevOps is to create a more responsive development, update, and upkeep strategy, as well as to keep development objectives in constant alignment with business ones. Continuous integration, continuous delivery, and continuous deployment were born to promote more agile strategies on the development side. The theory behind each are as follows: Continuous integration:  Merging all your developers’ code into one central repository at regular intervals to avoid code conflicts Continuous delivery:  Keeping code constantly ready for deployment without pushing it into production Continuous deployment:  Automatically pushing code updates into production after successfully passing testing Often, the term CI/CD is used to mean continuous integration/continuous delivery—ignoring continuous deployment—because the tho