Giter Club home page Giter Club logo

Comments (5)

wilkinsona avatar wilkinsona commented on August 11, 2024

Sorry, I'm struggling to see the connection between microservices and the use of a parent pom or a Git submodule. Can you explain in a bit more detail please?

One area where I can see microservices complicating things is in discovering and accessing the documentation. The best approach that I've heard so far is for each microservice to serve its own documentation from the same URI (/docs, for example). You can then piggyback on service discovery to also discover the documentation. Using hypermedia and linking to the service's documentation from its main entry point is another approach.

from spring-restdocs.

ccit-spence avatar ccit-spence commented on August 11, 2024

Your right, that was my confusion. The maven idea was somehow thinking that might be a way to create a docs site. Not that it was a good idea.

I could see using Zuul to route to the docs and maybe setting up a central docs UI with links to each services set of docs.

The main thing is I am finding centralized documentation to be a bit of a challenge with Microservices. I like the idea of keeping docs with each service; then providing a central UI to access them.

In the example you listed. I assume you have a route in the gateway that would like like this /api/service/** then within the api you have a static directory/resource /api/service/docs which would be the docs for each service.

For the centralized doc service have it utilize service discovery for listing docs for each service. This could then span to other none REST services if the same structure is implemented.

This sound close to the right track?

from spring-restdocs.

wilkinsona avatar wilkinsona commented on August 11, 2024

Yes, that's the kind of approach I had in mind

from spring-restdocs.

ccit-spence avatar ccit-spence commented on August 11, 2024

We will start working on this this week and see how it turns out. Sounds like it should actually be fairly simple. Seems as though the key is Discovery to include services within the main docs. Otherwise a point of contention will be hard coding everything.

I have not tried anything with Restdocs yet, does it support things like Feign and RestTemplate? My assumption is that each rel can be defined in the Mock setup.

from spring-restdocs.

wilkinsona avatar wilkinsona commented on August 11, 2024

does it support things like Feign and RestTemplate?

No. You use Spring Test's MockMvc API to drive the tests and generation of the documentation.

from spring-restdocs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.