Skip to content
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.

Additional candidate metadata #6

Open
aalmiray opened this issue Mar 10, 2014 · 9 comments
Open

Additional candidate metadata #6

aalmiray opened this issue Mar 10, 2014 · 9 comments

Comments

@aalmiray
Copy link
Contributor

I know gvm-sdk simply consume data comign from gvm's server side however I thought this would be a good place to start this discussion. Say someone builds a griffon client for gvm-sdk (hint, hint 😉); in order to make the app more appealing one would think it may display a logo and some other additional data that the gvm REST API does not expose (yet). Specifically I'm thinking of (at least) the following items:

  • name. We've got this already, that's the candidate name.
  • logo. Qualified list of URLs with small, medium, large, huge as qualifiers for example.
  • summary. One liner stating the candidate's purpose.
  • description. A few paragraphs (up to 3 maybe) in render friendly format (markdown perhaps?) with further details on the candidate.
  • url.

WDYT?

@marc0der
Copy link
Member

Love it! I'll add this to the backlog for my new gvm server (written in shiny new spring-boot).

@pledbrook
Copy link

So how many implementations has the gvm server now seen? 😄 BTW, what are the advantages of Spring Boot in this case? Not knocking the decision, just interested in the reasoning.

@aalmiray
Copy link
Contributor Author

I bet @smaldini would love to see an implementation using https://github.com/reactor/reactor 😉

:squirrel:

@pledbrook
Copy link

Nah, it has to be Reactor with something. I think he favours Ratpack atm.

@marc0der
Copy link
Member

@pledbrook this is going to be the first rewrite of the server. I favour spring-boot because it's well suited for micro services, allows me to write in groovy, and builds a fat jar making deployment on paas a breeze.

@pledbrook
Copy link

Ah, I thought you'd tried Ratpack and DropWizard (which also fit those benefits). I wondered if it was the Spring support itself that was significant.

@marc0der
Copy link
Member

Yes, that's also a big seller. Spring Data for Mongo is very very useful.

DropWizard was the other great contender. Ratpack not so much because it seems closer to web framework than MSA. Also, when I last used it, it didn't generate a fat jar, but an awkward gradle script stuck deep in the build folder.

@aalmiray
Copy link
Contributor Author

Right. Ratpack cna be very minimalistic. Good thing a Ratpack project is a valid Gradle project so you can use https://aalmiray.github.io/gradle-plugins/plugins/gradle-fatjar-plugin.html 😉

@marc0der
Copy link
Member

Thats true, but I still favour spring-boot more :D

On 11 March 2014 16:12, Andres Almiray [email protected] wrote:

Right. Ratpack cna be very minimalistic. Good thing a Ratpack project is a
valid Gradle project so you can use
https://aalmiray.github.io/gradle-plugins/plugins/gradle-fatjar-plugin.html [image:
😉]

Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-37314400
.

Marco Vermeulen
+44 7757 510 608

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants