Mockey
avaje-jex
| Mockey | avaje-jex | |
|---|---|---|
| 1 | 3 | |
| 116 | 19 | |
| - | - | |
| 0.0 | 4.7 | |
| over 2 years ago | 6 months ago | |
| Java | 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.
Mockey
-
Our KMP Journey
We rely heavily on Mockey to mock our api responses for testing and one of the first interceptor we ported to work with Ktor client. Below is sample code of our interceptor. We toggle the use of interceptor using debug preferences.
avaje-jex
-
Libraries other than Spring Boot for creating web APIs
I created https://github.com/avaje/avaje-jex ... with the hope of helping to move Javalin more in the Java direction but yeah, Javalin isn't going in that direction. So avaje-jex now will follow it's own path (as pretty much a web routing layer that abstracts over various http servers like jetty, grizzly etc with a java and loom focus).
-
is anyone want to join maintaining spark java framework?
Well, ultimately I instead ended up creating jex - https://github.com/avaje/avaje-jex
-
Practical intro into creating Virtual Threads with project Loom
The Jetty ones use Jex and Loom based Jetty ThreadPool implementation ... and note that this isn't how the Jetty folks themselves have been playing around with Loom (see their loom branch). However, testing this just now against the latest 19 EA in what I think is the worst case scenario for Loom has: Loom at 80 rps and Traditional at 90 rps. Worse case scenario for loom meaning there is NO WAIT AT ALL in the response and that we do not exceed the Traditional Jetty thread pool size (testing at 100 concurrent clients which is less than default 200 max Jetty thread pool). As soon as we introduce IO wait + exceed the traditional thread pool size in terms of concurrent activity is when we see loom win out.
What are some alternatives?
multiplatform-settings - A Kotlin Multiplatform library for saving simple key-value data
test-driven-learning - Learning tests
mock-box - Mock-Box is a lightweight and powerful mock library that supports testing.
rest - Jakarta RESTful Web Services
moko-resources - Resources access for mobile (android & ios) Kotlin Multiplatform development
RESTEasy - An Implementation of the Jakarta RESTful Web Services Specification
Apache Spark - Apache Spark - A unified analytics engine for large-scale data processing
manifold - Manifold is a Java compiler plugin, its features include Metaprogramming, Properties, Extension Methods, Operator Overloading, Templates, a Preprocessor, and more.
airlift - Airlift framework for building REST services
Grails - The Grails Web Application Framework
Netty - Netty project - an event-driven asynchronous network application framework