Good Morning!

mawning

morning 😭

tears?

Morning

Morning

Happy Pre-Friday everyone 🙂

Virtual Friday for me.... 🙂

So, question. I'm generating several "reports" (let's say maps for now) that are the results of hitting a database with queries. The queries are standalone and thus can be done in parallel.

Does this look okay? (keeping it simple...)

(let [report1 (future (report-service/report1))
      report2 (future (report-service/report2))
      report3 (future (report-service/report3))]
  {:report1 (deref report1 5000 nil)
   :report2 (deref report2 5000 nil)
   :report3 (deref report3 5000 nil)})

Looks good to me! Same approach taken here https://github.com/reborg/parallel#plet (my small lib)

neat

I was reading another function from your book yesterday Renzo

map (and filter and reduce)

🙂

that is making me think for the need to surface a timeout option

Morning.

Morning

timeouts are good 🙂

and a default if timeout reached 🙂

Morn’

As someone who uses Spring (for my Kotlin work). I'm super happy that finally they've come to their senses and dropped the horrible naming stragegy they were using:

https://spring.io/blog/2020/04/30/updates-to-spring-versions

https://youtu.be/CbFaMhl2t_Q

heh. that song still puts a smile on my face

morning

@dharrigan As someone who’s never used spring, what does it give you and what’s the tradeoff?

It gives quite a lot (talking mostly about spring boot here), full object lifecycle management, mostly it's all about IoC and dependency injection

spring boot comes with a lot of "starters" out of the box - for example, do you want to use kafka - just add spring-cloud-starter-stream-kafka to your deps

and it pulls it all in, configures appropriate listeners and does all the marshalling for you

or, perhaps you need RESTful APIs - spring-boot-starter-web

create an object, annotate the method with @GetMapping and away you go

again, takes care of the marshalling for you

so, it basically gives an opinionated way of doing things, hides all the complexity but exposes SPIs and hooks if you need to modify

but for 80% of the cases, it works for nearly all problem domains out-of-the-box.

leaves you to concentrate on writing the business logic.

Hmm, interesting, I see the appeal =)…

It's very popular

From my point of view it contains too much magic and is dog-slow

But it's very enterprise so I have to understand it

I used to use it a lot when it was all XML configuration, and I was a fan (after all, Java needed something for dependency injection). I returned to it after a break of a couple of years, and now there's way too much "action at a distance" and aspect-oriented "magic". It now seems to hide the application structure rather than documenting it.

I personally don’t see the issue with magic as long as you can dig a little and find out what it’s doing, if you can’t then it’s less, here are a bunch of sane defaults for various use cases and more I’m just going to try and always guess what you want. The latter can be really bad :(…

aspect-oriented as in modifying the classfiles to add in before/after/around method interceptors according to some annotations or recipe ?

With Sprint Boot - I've never had to write any xml, nor worry about AOP

They've removed XML as far as I know, it's all java config now

(or rather kotlin config, as that's what I use at work too )

Spring was sooo much better the crappy J2EE stuff that it replaced but that was a long time ago now it seems that it's gone some way to turning into that crappy J2EE stuff

for me it boiled down to the question > does it make me do things that I don't want to do? like force me to subclass their concrete class, or conform to their opinion about how to structure the classes and Spring (mostly) didn't boss me around

True - it often provided helper classes that you could extend_,_ but there was usually a non-invasive alternative.

I had problems with all the magic stuff going on in Spring boot.... never quite grogged it.

Spring Boot, oh blimey please no, not that.