sagan VS Gradle

Empeza con esto https://spring.io/

If you want to do web apps, I'd recommend Django (a python framework) https://docs.djangoproject.com/en/4.1/, but you can do Rails, or Phoenix, or Spring Boot, or whatever. It doesn't terribly matter *which* one you do, as they share characteristics, and, chances are, your company will be using a different one :). Just pick one and go. You can do it. You know a lot more than you think.

With the idea planted, and already internalized that I would use spring-boot to create our API, I needed to decide on which engine it would be built. I had been studying Unreal Engine for some time, but because I had more know-how in Unity and because I found this AMAZING weather system, I opted for our last alternative.

This is an introduction article on how to build a RESTful application in Kotlin using Spring Boot 3 and MongoDB Atlas.

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

Im stuck between just starting up a project, or if following some starter project for learning. I did a tutorial on the spring.io website, but thats about all I have done so far.

I've been following the guides at spring.io, but there's just so many guides there. My company has a template for starting new projects (includes frontend + backend + database) so I decided to start my project using it, thinking the basic guides I followed on REST APIs would help me but I quickly realized it's more complicated than I thought.

Thanks for the advice. I followed some guides on spring.io, but because I am using a template for starting new projects provided by my company, I found most of them couldn't really translate properly to the template.

Spring makes building web applications fast and hassle-free (spring.io). By removing much of the boilerplate code and configuration associated with web development, you get a modern web programming model that streamlines the development of server-side HTML applications, REST APIs, and bidirectional, event-based systems.

A ("shared") build service is kind of like a singleton, in that when you register one in any project, it's available in all projects as a single instance. (This unfortunately turns out not to be true, in some cases, when using composite builds, but can be worked around.) An actual singleton (global static instance) doesn't work at all, for the record—try it if you want to lose some sanity. Anyway, use a build service whenever you need global mutable state in your build.

When using build tools like Maven or Gradle, you can configure environment variables in the build scripts or configuration files.

For large projects, purpose-made build tools such as Gradle and Maven are preferred for managing the directory structure since they introduce additional semantics for managing test code and other programming languages (among lots of other things). Most IDEs can integrate with these build tools easily. If you're just starting out though, I wouldn't worry too much about these, you can visit them later.

Project Build and Management: Apache Maven 3 (3.9.5), Gradle 8 (8.3)

No wonder this had been raised previously, https://github.com/gradle/gradle/issues/15383

Ktor, a powerful web framework built with Kotlin, offers a lightweight and flexible solution for building web applications. In this article, we will guide you through the process of creating a Ktor project manually using Gradle and SDKMAN!. By following the steps below, you'll have a basic Ktor project up and running in no time.

The details regarding the code compiling would vary from one project to another. For that project, it seems that it uses Gradle (a helper tool) for compiling. Check Gradle's documentation for more information.

At the moment, Java 20 is the latest version, but Java 17 is the latest LTS release. It's usually best to use an LTS release, because the latest releases won't be widely supported. And that's true of Gradle too. You're using Gradle 8.0, but not even the latest version of Gradle (8.2) fully supports Java 20. You'll have to wait for Gradle 8.3 to use Java 20.