Question mostly about (acceptance) testing Microservices

• backstage

  125 26,317 10.0 TypeScript

  Backstage is an open platform for building developer portals

  

Now, you sound like you will have at least 10 microservices, potentially many more (I was in a team of 6 where we had 12), so you need to automate coordination; I'd recommend a service catalog like https://backstage.io/ which provides a lot of pre-built functionality. I've used a homegrown solution where everything was listed there, and we used schema-first code generation; service A publishes their up-to-date schemas there, and service B pulls them on a full build and uses openapi-generator or something similar to convert them to microservice-local code based on the local microservice requirements (we had some microservices that needed async bindings, and some that needed synchronous; same schema, different output). There's also AsyncAPI which works well for message-driven services.

• prism

  25 4,006 8.5 TypeScript

  Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations. (by stoplightio)

  

Re: schema-first, there's tools like https://github.com/stoplightio/prism that can do some heavy lifting for you; if you're willing to get your hands dirty you can create an openapi generator for cucumber/gherkin scripts.

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

Suggest a related project