Kafunk
Spring Boot
Kafunk | Spring Boot | |
---|---|---|
1 | 167 | |
159 | 72,870 | |
- | 0.7% | |
1.7 | 10.0 | |
- | 5 days ago | |
F# | Java | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Kafunk
-
Walmart is migrating the remaining F# code into Java
Performance.
Generally speaking, F# was actually very fast, and had nice concurrency support, but there were times that wasn't the case.
For example, in 2016 I was part of the initiative to rewrite the ad feed. We had to read in several Kafka topics, do some joining on our end, and emit to a separate Kafka topic. This isn't terribly hard to write, but we were dealing on the order of about ~100gb of data being pushed into memory. This is hardly "big data" stuff, but it's enough to highlight some issues.
Specifically, the built F# persistent map structure was simply too slow to get the performance we wanted. I really like that structure, it's really handy and nice, but I ended up having to make heavy use of the ConcurrentDictionary that was built into .NET. This wasn't that hard or anything, but it made me a little sad that I had to move to a mutable store to get the performance I needed.
There was also the fact that the `async` monad, while generally very good and useful, had bizarre bottlenecks that were hard to measure. It was difficult to know when the async task was actually started, and when you tried to measure performance bottlenecks you were really only measuring the scheduler, not the actual performance. This isn't really F#'s fault, this is an issue with any kind of cooperative scheduling system, but occasionally to get the performance we needed we'd have to move to lower level threads instead of the pretty monadic stuff. Microsoft eventually released the Task monad which generally performed a bit better.
There were other things here and there; the Kafka client libraries for .NET simply aren't as good as the Java ones. Jet actually open-sourced their own (https://github.com/jet/kafunk) which did make it a bit more functional and nice, but it had performance issues as well, so a lot of us ended up using Confluent.
There were little annoyances specific to F# as well; there's no real concept of a monad transformer, so if you wanted to do something like, for example, combine an Option and an Async into generalized syntax, you'd have to write your own wrapper monad thing, which wasn't that hard but was sort of ad hoc.
The general rule of thumb was that the first draft of software, we would try and keep as functional and pretty. If that was too slow, we allowed mutation but only within a function. If that was too slow, we'd allow global mutation but only with thread-safe stuff.
Spring Boot
- JHipster 8 - Analisando o código da nossa primeira aplicação monolítica - Parte 2/3
-
Walmart is migrating the remaining F# code into Java
- Usually manually wired and configured vs the spring boot "starter" pattern of having libraries that automatically do some of the manual setup work for you: https://github.com/spring-projects/spring-boot/blob/main/spr...
I wish more client library sets had the feature-matrix that the pulsar one does, because in practice most end up being the same: Java supports everything because it's either built in the same codebase or is the most used client and gets the most support, while the dotnet client codebase has many feature-requests or performance improvement issues, often leading to a "third-party client" being created.
- AI PR adds auto generated comments to whole Spring Boot Project
-
AI commented the entire Spring Boot codebase
https://github.com/spring-projects/spring-boot/pull/39754/co...
-
Spring Boot 3 And Java 17 Migration Guide
If you’re currently running with an earlier version of Spring Boot, I recommend that you upgrade to Spring Boot 2.7 before migrating to Spring Boot 3.0. It minimizes compatibility issues as much as possible.
- Spring Boot 3.2.0 Release Notes
-
The Game of Life, the Universe, and Everything: Java Virtual Threads in Action
Okay, we need to build the game? No problem, we will use Spring Boot and Swing!
-
Netflix Uses Java
It's weird that some people including you directly attack my competence. As a power user you should have plenty of experience getting something to work that is not properly document, does not work how the documentation promised it to, or has weird problems on top of it. Look at idiotic things like this:
https://github.com/spring-projects/spring-boot/issues/33044
Take any similar issue and you'll see a bunch of people who try to find a solution for them because they just aren't repeatable at all. The underlying issue is the auto configuration doing things you can't follow quite properly. It's like it wasn't mean to be understood. Issues like the one I linked above also show me that the spring dev crowd also doesn't understand the ecosystem anymore. The problem is complexity and automagic.
-
What's New in Spring Framework 6.1
An interested reader can decide for themselves:
https://github.com/spring-projects/spring-boot/tree/main/spr...
-
Secure Java URL encoding and decoding
Explicitly decoding URL query parameters occurs less often because many frameworks, including Spring Boot, handle decoding automatically.
What are some alternatives?
NetMQ - A 100% native C# implementation of ZeroMQ for .NET
helidon - Java libraries for writing microservices
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
Play - The Community Maintained High Velocity Web Framework For Java and Scala.
RawRabbit - A modern .NET framework for communication over RabbitMq
javalin - A simple and modern Java and Kotlin web framework [Moved to: https://github.com/javalin/javalin]
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
Quarkus - Quarkus: Supersonic Subatomic Java.
Rebus - :bus: Simple and lean service bus implementation for .NET
Jooby - The modular web framework for Java and Kotlin
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
ZK - ZK is a highly productive Java framework for building amazing enterprise web and mobile applications