You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@
4
4
Demonstrates using Spring Framework with Scala 3.
5
5
6
6
The biggest headaches of upgrading from Scala 2.13 to Scala 3 has been with the level of compatibility tools like IntellIJ offer, and the relatively small market share
7
-
it has of Scala projects and libraries. Builds sometimes slow to a crawl or hang or randomly fail, only to succeed after a second or third retry.
7
+
it has of Scala projects and libraries. Builds sometimes slow to a crawl, hang, or randomly fail, only to succeed after a second or third retry.
8
8
9
-
The jury is still out on whether the migration is worthwhile for established projects, but
10
-
as of 2025 I do feel like Scala 3 is the way to go for new projects.
9
+
The jury is still out on whether the migration is worthwhile for established projects, but I do feel that Scala 3 has reached the point
10
+
where it is the better choice for new projects.
11
11
12
12
:speech_balloon:**Questions / comments / suggestions are welcome in the [discussions](https://github.com/halfhp/ScalaSpringExperiment/discussions), or feel free to [contact me](mailto:halfhp@gmail.com) directly.**
*[Circe](https://github.com/circe/circe) - JSON serialization and deserialization
24
25
*~~ZIO~~ (Sticking with with Cats Effect out of preference, and because ZIO seems to have been [abandoned by its author](https://degoes.net/articles/splendid-scala-journey).)
* Flyway - Database schema definitions and migrations
28
29
* ScalaTest
29
30
* Mockito
30
31
31
-
[^1]: I chose Gradle over SBT initially out of curiosity. At this point I've used for several Scala projects now and have no regrets.
32
-
SBT I believe might have some minor performance benefits, but you really cant Gradle in terms of features and support.
32
+
[^1]: I've used for several Scala projects now and have few regrets. SBT I believe might have some minor performance benefits,
33
+
but you really cant beat Gradle in terms of features and support. Having said that, it is possible that some of the build
34
+
instability / Intellij bugginess I am experiencing is due to Gradle.
33
35
34
36
[^2]: So why Doobie and not one of the options that come packaged with Spring? Two main reasons: 1) Integrates seemlessly with Cats Effect and the IO monad, which is my
35
37
preferred tool for structured concurrency. 2) Doobie is oriented around writing pure SQL and producing results as immutable case classes which I prefer over ORM approaches etc. that involve things like Hibernate, JPA, "live objects", etc.
@@ -129,6 +131,7 @@ what happens under load in situations where there are fewer cores than threads,
129
131
## Spring Security
130
132
* Add OAuth2 request/ refresh tokens
131
133
* Add Oauth2 client to support third party authentication (Google, etc)
134
+
* Add JTI to JWT tokens to support revocation
132
135
133
136
## Async Rest Controller
134
137
Create an AsyncController that demonstrates adapting Spring's async programming model
0 commit comments