<@U98QEKBSS> Spring boot is definitely overkill, a...
# server
a
@Kenneth Spring boot is definitely overkill, and I've personally found extreme blocks for the simplest versions for things like authentication security, testing via Mockito, deploying with Docker etc. Not saying it's impossible, but I should have to struggle for 3 hours trying to make it work together per issue
k
I actually use Spring Boot daily at work, and it is pretty great in an enterprise environment.
a
*when working with Kotlin
Forgot to add that part
k
Is it painful to use Kotlin with Spring Boot?
a
I haven't had issues with Kotlin so far with Spring Boot, it works like a charm
s
It actually works great together, especially since Spring Boot 2.0
j
We use Spring Boot 2.0 with Kotlin here and it works great as well. Implementing oauth / spring security was a pain, but I think that may be more of a general problem than a Spring thing.
a
Awesome - I'll probs be asking questions this evening on that
@Kenneth but yeah, so far my experience has been a little painful - I'm trying it out myself building from the ground up and so far for me the documentation might not be up to date or something, I'm not sure. The tutorials definitely aren't
k
Is there anything specific that have been more painful than others?
a
I just settled down after a long trip - but I will raise the specific issues I've been having in a little bit
Right now, I'm stuck on Mockito testing, docker, and authentication
it's too many things to be stuck on so I'll be asking all the dumb questions tonight
d
@aman400 it might be a good idea to start with a working example and then adapt it. It sounds like you're taking on a pretty steep learning curve - attempting to sort out all that stuff when you're working from a blank slate is hard.
p
why are you still sticking to mockito?
mockito sucks
just use mockk
👍 2
and yeah, "authentication security" is not a simple concept at all, yet Spring Security manages to somehow make it managable
k
Didn't know about Mockk, I will check it out. What are the benefits over Mockito?
p
The benefits of MockK are that it is written in and for Kotlin. It's not just a low-quality wrapper for Mockito. Also Mockito itself is pretty old and it shows. The API is inconsitent and relaxed mocks by default are very error-prone. MockK has amazing API which makes mocking easy, you don't have to look up syntax all the time. It can also mock coroutines and functions.
a
@poohbar I was looking for it and I'll be damned I didn't find it. You got a link? I feel like the whole mockito for kotlin lib should just be marked "deprecated"
p
s
Channel #mockk
a
so many channels - thanks!!