[ad_1]
The place we got here from
Over the past decade now we have been transferring to Cloud Native deployments for many of our software and API deployment. This has principally been an effort to interrupt legacy monolithic software and repair fashions into what we generally confer with as microservices. Most of that transfer has been most profitable underneath Cloud Native applied sciences using containers and container orchestration. This transfer has been dealt with using Kubernetes, Docker, and different related applied sciences.
The present state
We now have utilized numerous advantages of transferring to a microservices mannequin utilizing Cloud Native applied sciences. We are able to iterate on particular items of our apps and companies without having to the touch different correlating and parallel apps and companies that assist present experiences to our finish customers. We are able to higher make the most of agile and lean methodologies of software program improvement. We are able to deploy dev environments extra simply and check extra continuously giving us the flexibility to maneuver quick and break issues.
The issue is, deploying and exposing our APIs with Cloud Native applied sciences has been a supply of safety breaches and penetration into our purposes and companies.
TLDR?… Enter APIClarity
So, we need to use Cloud Native applied sciences for all the advantages they carry to microservice software program improvement. Nonetheless, we additionally need to have higher visibility to see when our APIs are being utilized correctly (or improperly). This can assist enhance our safety posture. It is going to additionally enhance software program supply, and testing normally to our API companies which can be deployed.
That is the place APIClarity actually shines. APIClarity helps monitor API utilization and utilization by utilizing service mesh applied sciences, like Istio, to seize API endpoint site visitors. It does this with out having to change current API companies, which is the place service-mesh infrastructure is utilized.
APIClarity helps to sync present API utilization with current OpenAPI Spec docs. That is vital as a result of you’ll be able to then detect shadow or undocumented APIs that purposes or different companies are utilizing in your API microservice. It detects using zombie / deprecated APIs that ought to have been killed off. And it lets you be alerted when a discrepancy happens.
APIClarity lets you assemble OpenAPI specs by way of commentary of your APIs that don’t at present have an OpenAPI spec. That is big! As a result of you’ll be able to then improve your API companies to make the most of OpenAPI spec docs. Thus, permitting for higher documented APIs in your developer groups and prospects.
Take a look at this demo. You’ll see how APIClarity lets you monitor the API calls inside and outdoors your software service, and the way rapidly you may get began with including APIClarity to your software deployment utilizing GitLab.
To get began with APIClarity…
- Watch the quick Snack Minute movies to see how one can handle a number of APIs with the new open supply API observability instrument APIClarity
- Take a look at the positioning and docs
- Checkout the Github repo
If you happen to actually need to take it additional you’ll be able to make the most of this repo, the place we information you to construct a personal kubernetes cluster utilizing k3s and GitLab from scratch after which working by way of the identical course of as we used on this article to deploy our pattern app with GitLab CI/CD.
In my subsequent weblog, I’ll present you an instance of how we’re using GitLab CI/CD with Kubernetes, Istio, and APIClarity to deploy a pattern microservices app and management the lifecycle administration of our pattern software.
Â
We’d love to listen to what you assume. Ask a query or depart a remark under.
And keep linked with Cisco DevNet on social!
Twitter @CiscoDevNet | Fb | LinkedIn
Go to the brand new Developer Video Channel
Share:
[ad_2]
