Closed yada closed 1 year ago
The application for Microcks is ready for review🤞 As stated in the submission above, we have done two presentations to TAG App Delivery:
Project presentations
1st presentation to CNCF TAG App Delivery during pre-day meetup at KubeCon + CloudNativeCon Europe 2023, see:
2nd presentation (2023-05-17) as a follow-up during TAG App Delivery bi-weekly meeting, see:
I am writing to express my strong support for the Microcks project, which I believe would be an excellent addition to the CNCF. Microcks is an open-source tool that provides automated API testing, contract validation, and documentation generation for REST and SOAP-based APIs. It is designed to integrate with existing CI/CD pipelines and DevOps toolchains, making it easy to incorporate API testing into your development workflow.
Microcks supports a wide range of API testing frameworks, including OpenAPI, AsyncAPI, and GraphQL, and can generate API documentation in a variety of formats, including Swagger UI, ReDoc, and AsciiDoc. These features make Microcks an incredibly useful tool for developers and organizations looking to improve the quality and reliability of their APIs, and to streamline their API testing and documentation processes.
What's more, I know firsthand that Microcks is highly regarded by its users. Many customers initially considered it a "nice-to-have" tool, but soon realized that it was a "must-have" once they started using it. The feedback I have received from developers and organizations that have implemented Microcks has been overwhelmingly positive, and I believe that it has the potential to make a real difference in the industry.
I strongly encourage the CNCF to consider Microcks for acceptance into the organization. I believe that this project aligns perfectly with the mission and values of the CNCF, and that it could benefit greatly from the resources and support that the organization can offer. Thank you for your time and consideration.
Thanks @joshgav for mentioning Microcks in https://github.com/cncf/sandbox/issues/30 comments. We have noticed the AIP project and will join the next TAG App Delivery meeting on Wednesday June 21 to follow the presentation.
@yada presented Microcks to TAG App Delivery last month, all the details are in this issue: https://github.com/cncf/tag-app-delivery/issues/411
BTW, We have created the #microcks channel in the CNCF slack if you have any questions or would like to know more on the project 🙌 Thanks @amye for the support 👍
@amye or @TheFoxAtWork can you add the "App Delivery" label to this submission?
Looking forward for this! I too support Microcks being part of the CNCF. Representing the event driven architecture (EDA) industry, I do see great opportunities and potentials of Microcks from asynchronous APIs mocking and testing. There is very limited tooling in EDA for API testing and mocking and Microcks is the most mature in this space.
Hi folks - TAG App Delivery worked with @yada at Kubecon EU and at our May 17 meeting to learn all about Microcks; I'll share a report and recommendation here. In short, if CNCF wants to accept projects focused on cloud-native application development then Microcks is a good fit.
Background: Microcks' capabilities are valuable for developing microservices-oriented, cloud-native applications that communicate synchronously or asynchronously via structured transports and models like HTTP/JSON, GRPC/Protobuf, Kafka/JSON, et al. It aids in constructing such services by letting developers define an interface and semantics without writing a complete implementation of an API service, helpful for API-first development and test simulations in particular.
Microservices applications generally run on cloud-native platforms like Kubernetes or cloud services like AWS ECS or Fargate, and that would be the reason to include projects that support them like Microcks in CNCF. In terms of the functionality it enables, Microcks fits alongside existing projects like Dapr, GRPC and Konveyor in its goals of enabling cloud-native application development. As I mentioned in an earlier comment, its goal of enabling quality microservice/API development is similar to AIP's too (see cncf/toc#30) - perhaps AIP could develop some test cases for their patterns to include in Microcks.
FWIW Microcks might also be compared to CNCF's existing testing frameworks like LitmusChaos and ChaosBlade, though those are focused on resilience and "chaos" testing. Arguably such tests are part of application integration and delivery.
Also relevant, Microcks integrates existing and emerging open standards for API and service development such as OpenAPI, AsyncAPI, GraphQL, CloudEvents, Apache Kafka and more.
My only doubt has been around how CNCF wants to support projects aimed at application developers and cloud-native development. Of course we want them to grow and they're vital to the cloud-native ecosystem, but do we want to host them in CNCF or would they be better off in say Eclipse or Apache?
If CNCF does want to host projects that facilitate cloud-native app development then Microcks would be a great fit. Thank you @yada!
Thanks, @joshgav and the TAG App Delivery for the report and recommendation.
To TOC members and @justincormack 👇
Regarding the TOC review on June 13, 2023, please see below our answers and point of view regarding the questions/objections raised :
1/ We do not understand the analogy with the AIP project, except both are dealing with API! Microcks is a solution mature and in production which help enterprises to better use the CNCF ecosystem and create cloud-native applications for years see our adopter's usages: https://github.com/microcks/.github/blob/main/ADOPTERS.md and the comment from Tamimi: https://github.com/cncf/sandbox/issues/37#issuecomment-1589724813
IMHO, this is certainly the most important point and we hope that based on the information above and all details in our submission, the TOC can consider adding cloud-native application development tooling as a good fit in the CNCF. Community feedback clearly claims that Microcks helping them use to bring, create and maintain cloud-native workloads at scale is very valuable, see the testimonial from J.B Hunt: “ Accelerating development The developers of the project mentioned above saved at least 7 months using Microcks. They were not only able to work concurrently but also captured the exact business requirements specified by the product owner in the form of example request/response pairs. These persistent mocks can now be utilized in sandbox environments if needed. “ See for the full blog post: https://microcks.io/blog/jb-hunt-mock-it-till-you-make-it/
2/ Microcks is not a company, we just personally own and use the domain name for the maintainer's emails and project website. We are 100% community-driven and open source.
3/ Microcks is not a Red Hat project or has not been started as a Red Hat project. Microcks has been created in early 2015 and maintainers joined Red Hat in 2017 (both are now Postman employees and joined the Open Technologies program, see: https://microcks.io/blog/microcks-partners-with-postman/
4/ We have already presented twice to TAG App Delivery, comment updated to make it clear here: https://github.com/cncf/sandbox/issues/37#issuecomment-1523746787 BTW, this is a question in the submission form, see: Project presentations 1st presentation to CNCF TAG App Delivery during pre-day meetup at KubeCon + CloudNativeCon Europe 2023, see:
2nd presentation (2023-05-17) as a follow-up during TAG App Delivery bi-weekly meeting, see: CNCF TAG App Delivery Meeting Notes
Looking forward to the next steps and let us know if you have any questions or need further information.
Thanks & Regard,
/vote-sandbox
@amye has called for a vote on [Sandbox] Microcks
(#37).
The members of the following teams have binding votes:
Team |
---|
@cncf/cncf-toc |
Non-binding votes are also appreciated as a sign of support!
You can cast your vote by reacting to this
comment. The following reactions are supported:
In favor | Against | Abstain |
---|---|---|
👍 | 👎 | 👀 |
Please note that voting for multiple options is not allowed and those votes won't be counted.
The vote will be open for 7days
. It will pass if at least 66%
of the users with binding votes vote In favor 👍
. Once it's closed, results will be published here as a new comment.
I am writing to express my support in Microcks as a CNCF Sandbox project which seems to fit the criteria of “Independent projects that fit the CNCF mission and provide the potential for a novel approach to existing functional areas (or are an attempt to meet an unfulfilled need).”
I am a part of the the App Delivery TAG and have seen two presentations on this project. The key reasons I see this as a viable Sandbox project is because:
/check-vote
So far 27.27%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
3 | 0 | 0 | 8 |
User | Vote | Timestamp |
---|---|---|
justincormack | In favor | 2023-06-15 17:15:34.0 +00:00:00 |
RichiH | In favor | 2023-06-15 7:47:31.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-06-15 1:23:19.0 +00:00:00 |
Hi everyone! Here is Hugo from Red Hat. I am writing to support the Microcks submission as a sandbox project.
At Red Hat, we noticed a gap in cloud native solutions for API mocking and testing. That's why we decided to work with Microcks on those areas to enhance our story on API management. I have been contributing for several months to the project, mainly with the Docker Desktop Extension, to the point of becoming the primary maintainer for that component.
In addition, I have seen the value provided to other organizations using the solution to improve their developer experience. You can find adopters for the project from banks, transport, or the public sector. For this reason, I support their submission.
/check-vote
So far 63.64%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
7 | 0 | 0 | 4 |
User | Vote | Timestamp |
---|---|---|
mattfarina | In favor | 2023-06-16 17:53:51.0 +00:00:00 |
erinaboyd | In favor | 2023-06-15 20:48:35.0 +00:00:00 |
RichiH | In favor | 2023-06-15 7:47:31.0 +00:00:00 |
justincormack | In favor | 2023-06-15 17:15:34.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-06-15 1:23:19.0 +00:00:00 |
nikhita | In favor | 2023-06-16 5:42:17.0 +00:00:00 |
rochaporto | In favor | 2023-06-16 8:23:47.0 +00:00:00 |
Only repository collaborators can create a vote @ludovic-pourrat.
For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
Regarding Microcks as a good fit in the CNCF?
📢 We are delighted to have the support of friends and great companies like Bitergia to support our Sandbox CNCF application. Kudos to Diane Mueller for a deep GitHub data analysis regarding Microcks and CNCF connectedness for the last five years! 🚀
See this great visual, that report 10 CNCF projects with contributions by Microcks 🙌
This analysis also reports (for the same period) some very cool metrics from our community :
👉 https://www.linkedin.com/feed/update/urn:li:activity:7076562037866147840
Hi, I'm part of TAG App Delivery, Adding my support. Hope it's not too late for feedback to be considered. I was impressed by Yacine's presentation at the meeting. They've put a lot of work into making this a sandbox-worthy project and seem to have the momentum to continue. I'm also excited to play with this in the coming weeks ✊
+1 non-binding well run community, well connected to upstream projects (see: https://github.com/cncf/sandbox/issues/37#issuecomment-1597284946 for more details); nice plugin built in collaboration with the BackStage community and lots of enterprise traction (aka deployments) giving feedback and testing. Looking forward to seeing where this momentum take them next!
/check-vote
So far 72.73%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
8 | 0 | 0 | 3 |
User | Vote | Timestamp |
---|---|---|
mattfarina | In favor | 2023-06-16 17:53:51.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-06-15 1:23:19.0 +00:00:00 |
rochaporto | In favor | 2023-06-16 8:23:47.0 +00:00:00 |
dzolotusky | In favor | 2023-06-20 2:01:27.0 +00:00:00 |
erinaboyd | In favor | 2023-06-20 13:09:01.0 +00:00:00 |
nikhita | In favor | 2023-06-16 5:42:17.0 +00:00:00 |
justincormack | In favor | 2023-06-15 17:15:34.0 +00:00:00 |
RichiH | In favor | 2023-06-15 7:47:31.0 +00:00:00 |
Votes can only be checked once a day.
The vote passed! 🎉
81.82%
of the users with binding vote were in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
9 | 0 | 0 | 2 |
User | Vote | Timestamp |
---|---|---|
@TheFoxAtWork | In favor | 2023-06-15 1:23:19.0 +00:00:00 |
@nikhita | In favor | 2023-06-16 5:42:17.0 +00:00:00 |
@rochaporto | In favor | 2023-06-16 8:23:47.0 +00:00:00 |
@mauilion | In favor | 2023-06-20 16:55:28.0 +00:00:00 |
@justincormack | In favor | 2023-06-15 17:15:34.0 +00:00:00 |
@erinaboyd | In favor | 2023-06-20 13:09:01.0 +00:00:00 |
@mattfarina | In favor | 2023-06-16 17:53:51.0 +00:00:00 |
@dzolotusky | In favor | 2023-06-20 2:01:27.0 +00:00:00 |
@RichiH | In favor | 2023-06-15 7:47:31.0 +00:00:00 |
Closing with approved, new onboarding issue: https://github.com/cncf/sandbox/issues/197
Application contact emails
yacine@microcks.io, laurent@microcks.io
Project Summary
The Kubernetes-Native multi-protocol open source enterprise testing and mocking API solution.
Project Description
The Microcks project was launched in 2015 at the emergence of containers and Kubernetes and has been designed from the ground up with cloud-native and microservices principles and design patterns.
💡From day one, Microcks had the vision of a multi-protocol API ecosystem due to the ubiquitous nature of API. This is especially true at the enterprise level where the technology strata are built over the years.
As numerous API styles and protocols coexist, a uniform way to accelerate and secure their delivery is required! Our objective is to establish Microcks as the de-facto standard tool for delivering this unified approach the Open-Source way 🙌
Microcks allows you to simulate API, easily build on-demand test and sandbox environments, and check the conformance of your API application. It makes this consistent across HTTP, gRPC, WebSockets, GraphQL, Kafka, NATS, Google PubSub, and other popular patterns and protocols of your API lifecycle. Microcks is a cross-functional collaborative platform to ease the transition to microservices, API-based cloud-native applications.
For more information on the genesis, please see our Why Microcks?
Org repo URL
https://github.com/microcks
Project repo URL
https://github.com/microcks/microcks
Additional repos
https://github.com/microcks/microcks-operator https://github.com/microcks/microcks-backstage-provider https://github.com/microcks/microcks.github.io https://github.com/microcks/microcks.io https://github.com/microcks/microcks-ansible-operator https://github.com/microcks/microcks-jenkins-plugin https://github.com/microcks/microcks-postman-runtime https://github.com/microcks/microcks-docker-desktop-extension https://github.com/microcks/microcks-cli https://github.com/microcks/community-mocks https://github.com/microcks/hub.microcks.io https://github.com/microcks/test-github-action https://github.com/microcks/import-github-action https://github.com/microcks/api-lifecycle https://github.com/microcks/microcks-quickstarters
Website URL
https://microcks.io/
Roadmap
https://github.com/orgs/microcks/projects/1
Roadmap context
We are very ecosystem oriented and are open to interoperating with CNCF projects and open source projects to better serve our community users' interests.
Contributing Guide
https://github.com/microcks/microcks/blob/master/CONTRIBUTING.md See also our organization contribution guide: https://github.com/microcks/.github/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/microcks/.github/blob/main/CODE_OF_CONDUCT.md
Adopters
https://github.com/microcks/.github/blob/main/ADOPTERS.md
Contributing or Sponsoring Org
https://postman.com
Maintainers file
https://github.com/microcks/.github/blob/main/MAINTAINERS.md
IP Policy
Trademark and accounts
Why CNCF?
Microcks was started in 2015 at the emergence of containers and Kubernetes and has been designed with cloud-native and microservices principles and design patterns since day one.
It is important to put our project under the CNCF umbrella to demonstrate to the cloud-native community our commitment to manage Microcks expansion the open source way by joining the foundation and to assure our growing community of users and contributors of neutral governance. This is also a giant opportunity to encourage and grow community adoption and contributions. Last but not least, learning from others and giving back to the community is part of the maintainer's way of living!
Benefit to the Landscape
Microcks is a Kubernetes Native tool for API Mocking and Testing, and we aim to speed up, secure, and scale the company's API adoption, using an enterprise-grade universal API-first approach. Microcks is not only an API tooling “by developers, for developers” as it also aims to create a bridge between all the enterprise actors (business and product owners to developers) and assets (all kinds of API specifications and API). We think, that adding Microcks to the CNCF Landscape will help communities and enterprises to easiness cloud-native development, application life cycle management, and modernization.
Cloud Native 'Fit'
We think the project fits in the TAG App Delivery landscape since mocking tools like Microcks can speed up API and application integration tests and delivery.
Cloud Native 'Integration'
Depend on:
Complement and interoperate with:
Cloud Native Overlap
As far as we are aware, no existing CNCF project overlaps with Microcks.
Similar projects
Elsewhere, yes we have some similar open source projects for mocking (Hoverfly, Keploy et Mockitosh...) or testing (Pact...) but no overlap (from what we are aware off) with tools covering both (mocking + testing) and with such a large multi-protocol and multi-specs as Microcks.
As we often have the question of "Microcks vs Pact for contract testing", we have written a blog post for this purpose to try to clarify similarities and differences between the two projects. Please see: https://medium.com/@lbroudoux/microcks-and-pact-for-api-contract-testing-3e0e7d4516ca
Product or Service to Project separation
N/A
Project presentations
1st presentation to CNCF TAG App Delivery during pre-day meetup at KubeCon + CloudNativeCon Europe 2023, see:
2nd presentation (2023-05-17) as a follow-up during TAG App Delivery bi-weekly meeting, see:
Project champions
Josh Gavant - Lead TAG App Delivery
Additional information
This testimonial from J.B Hunt. is good community user feedback regarding why Microcks and the productivities gains that were realized: “ Accelerating development The developers of the project mentioned above saved at least 7 months using Microcks. They were not only able to work concurrently but also captured the exact business requirements specified by the product owner in the form of example request/response pairs. These persistent mocks can now be utilized in sandbox environments if needed. “ See for the full blog post: https://microcks.io/blog/jb-hunt-mock-it-till-you-make-it/