just my 2c, ofc 🙂

thanks @dave

From our experience, Cassandra is very resource-hungry

all the jetbrains team tools use Cassandra yes? meaning

From our experience

is quite a large pool of experience.

No, not all. But we have some.

Is redis a good option for longer term storage? I was always under the impression it was used for more for transient data like caching/sessions

There's nothing that says Redis has to be transient. The one requirement is that all the data must fit in memory, but it can be backed by either an append-only replay log, or via snapshots, that both persist data.

Maybe Prometheus?

i wonder what your long-term storage requirements are for these - if each row is fairly small you might be able to use something like kafka, with a reader cache that just holds the latest updated row for your frequent queries.

advantange there is also if you end up with more advanced query requirements you can still add that in later

kafka-streams could essentially create some materialized views of sorts for some use cases

thanks @gjesse

99% of the time I will query last row for each user

do you consider the ability to set a context-path for a server an important feature?

1️⃣ yes 2️⃣ no

1

in this new micro service era, with apps running in embedded containers, i don't consider it an important feature

@agomez how do you solve different services on the same domain?

with a reverse proxy (apache, nginx) routing to different micro services, each one running in its own embedded container

yup, fair enough

that's a very good alternative

that's what i'm running right now in production 😉

Microservices are for heavier loads, and server clusters that can spread them out. For alot it might be enough to have one api service around, which can then get messy without context paths....

I did Kotlin workshop yesterday When there are clear benefits for Android from Kotlin I got questions from BE people is it worth since java8 is there My answer was “I think so, since you’re not only writing streams and lambdas” But can some BE person share his answer?

terseness, data classes, delegation, smart casting, extension functions, more complete standard library, modifiable/unmodifiable collection types - plus all the stuff coming up (or experimental) - coroutines, immutable data structures, reflectionless serialisation, native

there's loads of things that make it nicer than Java

the ability to write DSLs

But also that none of it feels like language clutter - it's all well reasoned about

Thanks!

I forgot to mention that some pain/gain is solved by Lombok for them