For example, if I had a project that required I spin up twenty new virtual machines, I could go to the Azure website and manually add one, answering all the questions and going through all the wizards, then another following the same steps, and then finally two hours later, I am done. Even though Microsoft Azure and Amazon AWS have a pretty frontend, they are just a set of exposed APIs. Write once, make money from everyoneįor developers, using APIs is very powerful and dramatically reduces the risk of writing buggy code, and it is a boon to organizations offering their APIs to sell their services. To the person writing the app, they are using whatever language they are comfortable using and calling a “CreateCustomer” API that exists in your corporate network or the cloud. Going back to that example where you write an API to create a customer, that code might check for a valid email address, ensure there are no duplicates in the database, create a new record in that database, and send user-friendly messages back to the calling code. Developers want other developers to use their code and not have to understand the underlying functionality. If you follow my writings on this topic, APIs continue to grow in popularity as software developers write their code to be shared with others, be it for internal use, free, or as a paid service. APIs are an abstraction layer on top of your code that allows anyone (with access) to call your code in nearly any language. For example, your reusable code in JavaScript may not be as easy to use if you have other code written in C# or Swift. If you ever developed code, you probably wrote pieces of code you can reuse, but it was probably limited to the language you wrote it in. ![]() Still, it is becoming more deliberate as organizations realize the code can be exposed as APIs. Writing a single source of code to use everywhere is not new. If there is an error in the signup process, that code always returns the same error message or warning, and any version of the app can display the same information. That signup form might look one way on a browser and completely different on a mobile device, but it is the same exact code that processes the request and writes it to the database. For example, let’s say you have an app that enables a customer to sign up for your website. This type of architecture starts with writing the business logic once and then reusing it wherever it is needed. Instead, developers are thinking in terms of a service-oriented architecture. Gone are the days - well, hopefully - where you have multiple developers writing the same code for the same purpose. If you are writing code today, you are probably architecting it for high levels of reuse. ![]() The popular Postman application programming interfaces development platform has gone back to its web-based roots and introduced Postman for the web, a breakthrough browser interface to make creating, using, and testing APIs easier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |