apiclarity
microservices-demo
Our great sponsors
apiclarity | microservices-demo | |
---|---|---|
9 | 10 | |
471 | 3,523 | |
1.7% | - | |
4.0 | 0.0 | |
8 days ago | 5 months ago | |
Go | Python | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
apiclarity
-
Two approaches to make your APIs more secure
We'll install APIClarity into a Kubernetes cluster to test our API documentation. We're using a Kind cluster for demonstration purposes. Of course, if you have another Kubernetes cluster up and running elsewhere, all steps also work there.
-
How to Get Started with Open Source
If you go to APIClarity, the first thing you’ll see is the source code (Figure 1), followed by some documentation at the bottom.
-
Risk scoring your API Specification with Panoptica
This feature is available in the open-source tool APIClarity, as part of the OpenClarity initiative.
-
Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
Hi, I would also like to add another tool I'm contributing to at work (cisco) called APIClarity [1]. It aims at reconstructing swagger specifications of REST microservices running in K8S, but can also be run locally.
This is a challenging task and we don't support OpenAPI v3 specs yet (we are working on it).
Feel free to have a look, and get ideas from it :)
We'll also be presenting it at next Kubecon 2022.
[1]: https://github.com/openclarity/apiclarity
- Microservices API challenges
-
How to Use OpenAPI for Secure and Robust API Integration
For example, APIClarity is a tool that observes all of the API traffic within your Kubernetes environment. Based on traffic observation, APIClarity infers an OpenAPI description for those APIs. This is especially helpful if the API creator never defined or provided such a description. It also surfaces potential problems with existing APIs, such as requests made to undocumented, shadow APIs or continued use of deprecated, zombie APIs. If you’re getting started on the path toward OAS compliance, then tools like APIClarity can be a great source of insight and observability.
-
Watching the Requests Go By: Reconstructing an API Spec with APIClarity
The fundamental first step to solving this problem is to create an API spec and use it to audit and document the APIs your apps use. Ideally, we would create an API spec simply by observing API traffic in real-world applications. In the past, there was no simple, scalable, and open-source tooling capable of doing this. Now, we have APIClarity—an open-source API traffic visibility tool for Kubernetes (K8s) clusters. It’s purpose-built to address the gap and enable API reconstruction through observation.
- Reconstruct Open API Specifications from real-time workload traffic seamlessly
microservices-demo
-
How to create a django microservices monorepo?
As an inbetween beginner and advanced you can look at this project - https://microservices-demo.github.io/ its more practical and again uses Python.
-
How to get Kubernetes Ingress Port 80 working on baremetal single node cluster
I'm new to kubernetes world. I got sample kubernetes deployments (like sock-shop) working end-to-end without any issues. I tried NodePort to access the service but instead of running it on a different port I need to run it exact port 80 on the host. I tried many ingress solutions but didn't work.
-
What kind of web application can I create to test it on Kubernetes?
Here's an example app that fits all of the criteria above. Can be used as a good reference point. https://github.com/microservices-demo/microservices-demo
- A dummy website for school project?
- Open source microservice based apps
- Discussion: Any available open source application for Kubernetes hands-on?
- Any example kubernetes applications I can reference?
-
Watching the Requests Go By: Reconstructing an API Spec with APIClarity
1) Deploy the Sock Shop app in our K8s cluster. While we’ll use Sock Shop as our example application, you can deploy your own app to your cluster and still follow along. 2) Deploy APIClarity in our K8s cluster and configure monitoring 3) Observe API traffic on the APIClarity dashboard 4) Review and create an API specification and view the generated OpenAPI spec in Swagger format. 5) Identify deviations from an API spec along with usage of shadow and zombie APIs. 6) View and filter API events
-
Examples of complex architectures deployed with Docker/Kubernetes
Depending on what you want there is Microservice demo from Google or Sock Shop from Weaveworks.
-
What are some pre-made projects that I could use to practice on?
There are sample application that you could deploy, for example https://github.com/microservices-demo/microservices-demo
What are some alternatives?
oasdiff - OpenAPI Diff and Breaking Changes
emojivoto - Example application to help demonstrate the Linkerd service mesh
Nacos - an easy-to-use dynamic service discovery, configuration and service management platform for building cloud native applications.
example-helm-go-microservice - Example Go microservice with Helm chart
api-firewall - Fast and light-weight API proxy firewall for request and response validation by OpenAPI specs.
examples - Kubernetes application example tutorials
kusk - CLI for Kusk Gateway related functionality
DevSecOps-Studio - DevSecOps Distribution - Virtual Environment to learn DevSecOps
openapi-preprocessor - An authoring tool for OpenAPI specifications
microservices-demo - Sample cloud-first application with 10 microservices showcasing Kubernetes, Istio, and gRPC.
meshery - Meshery, the cloud native manager
awesome-devsecops - An authoritative list of awesome devsecops tools with the help from community experiments and contributions.