Tech Stack Discussion

[arunkpatra]

Are you in the process of envisaging a tech stack? How do the following sound? Just some thoughts...

Options

• Programming Language: Options

  • Go: Pros - Blazing fast, low runtime footprint, becoming popular fast, great for microservice implementation, adoption is headed north. Cons - Not too many developers at the moment. Tools and frameworks around Go are not as widespread as other platforms like Java.
  • Java: Pros - Robust, tons of frameworks and tools, rich ecosystem, great for microservices. Cons - tends to have a heavier runtime memory footprint than other nimbler platforms.

• Build Tool for DFD-Tool(internal to DFD-Tool)

  • Maven - Everybody loves and knows Maven. Tons of plugins.
  • Gradle - Simply awesome and extends all of Maven's goodness with an equally rich set of plugins.

Notes

If Java, then most probably Gradle or Maven. If Golang, then probably Go native build tool. Gradle plugins exist. Travis CI supports Golang well. But Travis-CI will cost unless project is "public"

[AbhideepChakravarty]

I agree with what you mentioned in the pros and cons.

There are one more concern: What do the available contributors are comfortable in?

I have personally worked on Gradle decent enough to run the project. Go, I do not know. Never tried yet. Though I have committed the code based on Springboot and Maven. I am open to any tech stack as far as contributors are ready to code in that language.

[arunkpatra]

@AbhideepChakravarty I would think, given the nature of Vicki and what it is supposed to do (plus the contributor inclination), Java + Spring Boot + Maven is just fine. There is no real need for the performance improvements (and runtime footprint optimization) that Go could bring as of now. As regards the build tool, we could consider migrating to Gradle when we like; in any case its 100% compatible with maven produced artifacts. However, IMHO, I found Grade to be future forward in many ways. Here's an issue I raised in another repo https://github.com/codecentric/spring-boot-admin/issues/1438

[eclatian-superadmin]

I agree. Moving to Gradle would not be a pain. It would be simple to do. Certainly we can migrate to Gradle. I am keeping this issue open for any tech discussion.