forked from shreya-gb/Cloud-Native-Hackathon
-
Notifications
You must be signed in to change notification settings - Fork 0
/
blog.html
64 lines (61 loc) · 6.45 KB
/
blog.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Document</title>
<link rel="stylesheet" href="blog.css">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css" integrity="sha384-Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm" crossorigin="anonymous">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Baloo+Tamma+2&display=swap" rel="stylesheet">
</head>
<body>
<h1 class="text-center" style="font-family: 'Baloo Tamma 2', cursive; font-size: 5em; margin-top:20px ;">BLOG SECTION</h1>
<div class="container mx-auto">
<div class="card">
<div class="infos">
<p class="text"><b>Everyday Examples of APIs</b>
<br> API helps developers quickly deliver information to consumers and is used every day in today’s world. From shopping online, browsing a social media app, or playing a game on your smartphone. Every time you visit a page online, you’re interacting with API. Here are some real-world examples of how you interact with API and may not even realize.
Going to a bank.
Think of yourself as a user and a bank teller as an API, while the bank is the system you interact with. When you want to take some money out of your account, you walk up to the teller(API) and say “I’d like $1,000 from this account”. The teller (API) then goes to the back, tells the bank manager (the system) “Mr/Ms.X would like $1,000”, the bank manager (the system) gives the teller (API) $1,000 who eventually gives it to you. As you can see the API, is a messenger between your needs and the system.
Searching for hotels.
When you go onto a travel site, it may be linked to 10 other travel sites to find the best deal for you. When you input details like Atlanta, 2 nights, 1 Room, you send this request to those 10 different travel sites. The API takes your request for that specific location, date range, and room and pings the 10 sites, who send back the deals they have found. You look through the 10 deals and pick the best one. Again, the API is a messenger for your requests.
Finding a Facebook profile.
Stalking your ex? Hopefully not, but thanks to APIs, you can do it easily! If you type in “John Smith” on Facebook, the API informs Facebook’s servers that you’re looking for John Smith. Facebook then sends you a list of all the profiles that match that name (with factors like vicinity to you, or mutual friends). Now you can find John Smith!
</p>
<a href="#" class="btn btn-light">Explore API</a>
</div>
<img src='vector.jpg' style="width:150%;" alt="stars on sky">
</div>
<div class="card">
<div class="infos">
<p class="text"><b>API Evolution for REST/HTTP APIs</b>
<br>API evolution is making a comeback these days with GraphQL and gRPC advocates shouting about it. Whatever API paradigm or implementation you subscribe to, evolution is available to you. REST advocates have been recommending API evolution for decades, but in the past I failed to understand how exactly to handle evolution.
Luckily, as always, tooling and standards for HTTP have been improving, and these days API evolution is a lot easier to wrap your head around.
API evolution is the concept of striving to maintain the "I" in API, the request/response body, query parameters, general functionality, etc., only breaking them when you absolutely, absolutely, have to. It's the idea that API developers bending over backwards to maintain a contract, no matter how annoying that might be, is often more financially and logistically viable than dumping the workload onto a wide array of clients.
At some point change cannot be prevented, so at that time evolution suggests you provide sensible warnings to clients, letting them know if a feature they're using is going away, and not bothering them otherwise.
Evolution involves thinking a little differently on how you approach change. Often there are simple things you can do to keep clients ticking along, and whilst clients will have to change at some point, the whole goal here is to allow them a decent amount of time to make that switch, with the minimal change possible during that change, and no lock-step deploys required.
</p>
<a href="#" class="btn btn-light">Explore API</a>
</div>
<img src='vector.jpg' style="width:150%;">
</div>
<div class="card">
<div class="infos">
<p class="text"><b>Self-Service APIs</b>
<br>The strategies listed above aren’t rocket science. In fact, they’re things that many API-first companies are already doing. However, it might not immediately be readily apparent to newcomers why these tactics are necessary. Hopefully, if you’ve read this far, that picture will be clearer now.
Marketing an API-centric SaaS has a lot in common with marketing other SaaS products, or any other product for that matter, but there are nuances associated with it. Considering these nuances, and increasing your service’s usability, is the best way to maximize the chances your API has of being successful. Making your API more self-service is also a surefire way to decrease one-on-one customer support, thus reducing cost!
</p>
<a href="#" class="btn btn-light">Explore API</a>
</div>
<img src='vector.jpg' style="width:150%;" alt="desert">
</div>
</div>
<script src="blog.js"></script>
<script src="https://code.jquery.com/jquery-3.2.1.slim.min.js" integrity="sha384-KJ3o2DKtIkvYIK3UENzmM7KCkRr/rE9/Qpg6aAZGJwFDMVNA/GpGFF93hXpG5KkN" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.12.9/umd/popper.min.js" integrity="sha384-ApNbgh9B+Y1QKtv3Rn7W3mgPxhU9K/ScQsAP7hUibX39j7fakFPskvXusvfa0b4Q" crossorigin="anonymous"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js" integrity="sha384-JZR6Spejh4U02d8jOt6vLEHfe/JQGiRRSQQxSfFWpi1MquVdAyjUar5+76PVCmYl" crossorigin="anonymous"></script>
</body>
</html>