#vert.x

[openbooth]

Quarkus の HTTP レイヤーのスレッドプールについて - 赤帽エンジニアブログ

Quarkus の HTTP レイヤーのスレッドプールについて - 赤帽エンジニアブログ

追記: こちらの記事は執筆時点(2019/12/20)での Quarkus 最新バージョンであった 1.0.1.Final の動作を元に記載されていました。しかし、その後に以下の修正によって Quarkus 1.1.0.Final 以降からは、Quarkus RESTEasy で

[openbooth]

Eclipse Vert.x 4 milestone 5 released!

https://vertx.io/blog/eclipse-vert-x-4-milestone-5-released/

[openbooth]

Vert.x TCP Server load balancing feature is awesome

https://medium.com/@yazidaqel/vert-x-tcp-server-load-balancing-feature-is-awsome-8cbab6899af

[ankaapmo]

How to Work With Multiple Verticles and Communication in Vert.x - #Ankaa

How to Work With Multiple Verticles and Communication in Vert.x As mentioned in the previous article, Vert.x is an event-driven, non-blocking toolkit. It was designed for asynchronous communications. In most cases, you need to work with multiple verticles in your applications. You also need communication between these verticles in these cases. In this... https://ankaa-pmo.com/how-to-work-with-multiple-verticles-and-communication-in-vert-x/ #Eventbus #Java #Messaging #Tutorial #VertX #Verticle

[aegissofttech]

If you are familiar with the concept of node.js then you must be excited to know about Vert.x system, introduced by Java experts as a new addition to open source projects.

[zxsu]

oh, my god, oh, my god. Just elegant as Node.js, but like it said, more polyglot.

[techkrab]

W1

The Best of 2014

End of the year is great chance to remind best technologies of the year 2014:

MSA & Vert.x & Hazelcast because they show the right way of making applications

Gulp.js makes build tasks on frontend just little bit easier

ES 6 & ES6 transpilers moves JS in nice direction

asyncio learns me a lot about async approach

Swift as great example of pushing the platform development forward

Java 8 that's one small step for mankind, one giant leap for Java developers

The list is highly subjective so don't take it too serious.

[attackio]

turtle.io vs nginx vs express vs vert.x

I revised my benchmark method for these servers (disabled stdout), and switched to a slightly weaker i7 CPU. The results show that only vert.x is in a position to beat turtle.io, but it's inconsistent availability caused the test to fail multiple times, before I did a final run to collect results in a single screen (only cropped out socket errors). https://www.flickr.com/photos/deviation/15396125973/ Transaction: turtle.io - 1,498.38/s nginx - 1,115.62/s express - 1,144.67/s vert.x - 1,640.76/s (failed to complete) Concurrency: turtle.io - 99.25 nginx - 26.58 express - 42.32 vert.x - 65.62 Overall I think this type of test represents real world usage, and turtle.io is the clear winner at this hardware spec. This also shows how different node.js modules can impact performance, as turtle.io & express simply wrap 'http'.