BlockHound
spring-native
Our great sponsors
BlockHound | spring-native | |
---|---|---|
6 | 19 | |
1,297 | 2,772 | |
1.3% | - | |
7.4 | 8.6 | |
6 days ago | about 1 year ago | |
Java | Java | |
Apache License 2.0 | 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.
BlockHound
- Is there a good way to monitor code for blocking operations?
-
Reactive Backend Applications with Spring Boot, Kotlin and Coroutines (Part 1)
There is a great tool called Blockhound we can use to detect if/when we have a blocking call in our application. This way, we can ensure that we don't break the non-blocking nature of our application by mistake while developing new features. Setting it up is fairly straightforward.
- Using Java's Project Loom to build more reliable distributed systems
-
3 Reasons Why All Java Developers Should Consider Quarkus
There's even a test library to detect them: https://github.com/reactor/BlockHound
-
BlockHound: how it works
One of the talks in my current portfolio is Migrating from Imperative to Reactive. The talk is based on a demo migrating from Spring WebMVC to Spring WebFlux in a step-by-step approach. One of the steps involves installing BlockHound: it allows to check whether a blocking call occurs in a thread it shouldn't happen and throws an exception at runtime when it happens.
-
Kicking Spring Native's tires
The first step is to make the application compatible with GraalVM. We need to remove Blockhound from the code. Blockhound allows verifying that no blocking code runs in unwanted places. It's a Java agent that requires a JDK, not a JRE. It's great for a demo, but it has nothing to do with a production application.
spring-native
-
Measuring Java 11 Lambda cold starts with SnapStart - Part 4 Using Spring Boot Framework
It was probably not a very good idea to write Lambda using Java programming language and Spring Boot Framework. Despite the well-spread usage and knowledge of this framework, the fact that Spring (Boot) heavily uses reflection and takes time to start the embedded Web Application Server led to very big cold starts which we'll explore in the next section. But now with SnapStart on AWS and GraalVM Native Image Support we have two more options how to optimize those cold starts. So let's explore how to write Lambda function using the Spring Boot. The code of this sample application (the same as for the first 3 parts but rewritten to use Spring Boot) can be found here. It provides AWS API Gateway and 2 Lambda functions: "CreateProduct" and "GetProductById". The products are stored in the Amazon DynamoDB. We'll use AWS Serverless Application Model (AWS SAM) for the infrastructure as a code.
- Compile the Minecraft Server (Java Edition) to Native with GraalVM Native Image
-
Introducing Spring Native for JHipster: Serverless Full-Stack Made Easy
During this experience, I was surprised to find that Spring Native doesn't support caching yet. I believe this support will be added by the community soon. In the meantime, if you're looking to start/stop your infra as fast as possible, you probably don't care about caching. Caching is made for long-lived, JVM-strong, JVM-loving apps.
- Spring Native – Native Executables for GraalVM Image Compiler
-
Podrá Spring Native revivir a Java?
fuente: https://spring.io/blog/2021/03/11/announcing-spring-native-beta
-
Annotation-free Spring
As I just found out thanks to a comment from another Redditor, spring-aot will be getting some functional configuration compile time generation support in Spring Native's next release
-
Curious about opinions of the best cloud native microservice Java framework
Not sure how far they are currently, but have you heard of Spring Native? https://spring.io/blog/2021/03/11/announcing-spring-native-beta
-
"Java Guitar Hero!", — Hanno Embregts
I have to say Spring. Because it is so mature and well-documented. Sure, it is bloated sometimes and not very well-suited for small JAR packages. And I have tried other frameworks as well, but I find that I keep returning to Spring. Especially since Spring keeps adding features that caused competing framework to have an edge over Spring, like native images with Spring Native for example.
-
Kotlin Team AMA #3: Ask Us Anything
Our next steps are : provide great Kotlin/JVM/Native (Native with Kotlin JVM via GraalVM native images) support via https://github.com/spring-projects-experimental/spring-native/, empowering multiplatform development (with Kotlin/JS frontend for example), translating Spring Boot documentation to Kotlin (via a contribution from Kotlin team), make sure that some APIs like WebTestClient currently broken with Kotlin due to some type inference bugs with recursive generic types become usable.
-
Is it right to use Spring & Spring boot?
I doubt micronaut has better runtime performance. You're probably talking about startup time and this point is moot with either https://github.com/dsyer/spring-boot-auto-reflect Or https://spring.io/blog/2021/03/11/announcing-spring-native-beta
What are some alternatives?
imperative-to-reactive - Shows how to migrate from a Imperative Programming model to a Reactive Programming model step-by-step, while keeping caching
ktor - Framework for quickly creating connected applications in Kotlin with minimal effort
lucene-grep - Grep-like utility based on Lucene Monitor compiled with GraalVM native-image
Quarkus - Quarkus: Supersonic Subatomic Java.
reactive-kotlin-weather-api
Micronaut - Micronaut Application Framework
agroal - The natural database connection pool
kotlinx.serialization - Kotlin multiplatform / multi-format serialization
reactor-core - Non-Blocking Reactive Foundation for the JVM
Spring Boot - Spring Boot
Flyway - Flyway by Redgate • Database Migrations Made Easy.
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM