Skip to content

Example with a simple microservice #1

Open

Description

@alejogutierrez

Hi I was looking to the implementation but still don't know how to interact with a service.
It is possible to see an example with a simple service?
Also a license would be awesome, thanks

Activity

  1. dusterio commented on Feb 2, 2017

    @dusterio
    Contributor

    I've just added a license - thanks for noticing this! :)

    Sure, we can provide an example. Does your simple microservice have Swagger documentation?

  2. alejogutierrez commented on Feb 2, 2017

    @alejogutierrez
    Author

    Well not really, in fact I found your repo because right now I'm moving from a monolitic Laravel app to microsevices written in Lumen.
    So does it mean that you have to use an specific modeling lang like swagger o RAML?
    Thanks again

  3. dusterio commented on Feb 2, 2017

    @dusterio
    Contributor

    You can either do it manually by providing your API gateway routes in GATEWAY_ROUTES environment variable, or you could parse Swagger JSON automatically. Swagger is just a nice way

  4. alejogutierrez commented on Feb 2, 2017

    @alejogutierrez
    Author

    Fine I'm going to take a look using swagger.

  5. reindeer77 commented on Feb 8, 2017

    @reindeer77

    I agree that it would be awesome to have some configuration examples (in my case swagger based microservice, but any further hint would be really appreciated) Thanks!.

  6. dusterio commented on Feb 8, 2017

    @dusterio
    Contributor

    Sure, you are right. Will add some examples tomorrow!

  7. moon0326 commented on Jun 9, 2017

    @moon0326

    @dusterio Hi Dusterio, where you able to add examples? The doc really does not make sense. I'm pretty sure that no one can run the full example, especially Swagger parts. It would be nice to have working examples with Swagger support.

  8. dusterio commented on Jun 9, 2017

    @dusterio
    Contributor

    @moon0326 I did but perhaps it wasn't enough :) I will review the documentation today and make sure it's comprehensive!

  9. moon0326 commented on Jun 9, 2017

    @moon0326

    @dusterio Thank you so much!

  10. dusterio commented on Jun 20, 2017

    @dusterio
    Contributor

    @spacecomx your microservices are expected to expose Swagger documentation endpoints (version 1), all actions will be imported upon start. routes.json is an internal, auto-generated file - a result of parsing of those Swagger endpoints.

  11. dusterio commented on Jun 20, 2017

    @dusterio
    Contributor

    @spacecomx I've just checked and Petstore is only provided in Swagger v2, it didn't exist till v2 I suppose. I guess it's time to add Swagger v2 support to Vrata.

    The reason I stuck with v1 only originally is - all major frameworks I checked at that time (~6 months ago) only had packages for v1.

  12. dusterio commented on Jun 20, 2017

    @dusterio
    Contributor

    @spacecomx I'll check tomorrow! if it's something simple (the difference is not too big) - I will add a v2 parser tomorrow :)

  13. rizwanmcs commented on May 24, 2018

    @rizwanmcs

    where we will define routes mapping in this project?

  14. harunnryd commented on May 28, 2018

    @harunnryd

    @dusterio Hi, where you able to add examples? :(

  15. agungsugiarto commented on Dec 27, 2019

    @agungsugiarto

    no example with swagger :(

  16. eddycastillon commented on Aug 18, 2020

    @eddycastillon

    Thank you so much for this awesome gateway.  I am trying to use this one however I have a couple questions about swagger. Until I know there are two ways to generate documentation for an API using swagger.

    1 - Using the public swagger editor: https://swagger.io/. It  generates API documentation and lets you share and collaborate  with people. I am able to export my documentation but I do not know how to use  the exported  documentation ( swagger.json ) to discover it. through the gateway.  I think I need to create a controller, route ,etc.

    2 - Using some composer packages that generates that documentation. To generate the documentation , basically you need to use the swagger notation in each controller and function. The package exposes your documentation so the gateway can discover the service.

    Based on your experience, what is the best approach to document an API.  If you use some composer package for lumen,  Could you share the name please.

    Thank you

  17. harunnryd commented on Aug 18, 2020

    @harunnryd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions