Vert.x is a tool-kit for building reactive applications on the JVM.
Showing 3 of 3 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Jayamine Alupotha
<p>Vert.x is a toolkit for the Java Virtual Machine enabling the implementation of reactive, highly concurrent, polyglot applications. Thanks to its eventbus, any application can interact with Vert.x applications. The TCP EventBus bridge is a bridge built on top of TCP, meaning that any application able to create sockets can use the EventBus from a remote Vert.x instance. The main project idea is to create TCP EventBus clients for C , Rust , C# and Python. For each language, a library will be developed in order to let an application developed with the language to interact with the Vert.x Event Bus easily.</p>
Mentors: Student: sczyh30
<p>Motivation for Proposal / Goal:</p> <p>Vert.x is an excellent full-stack toolkit which can help us build FRP-sytle, high concurrent, scalable applications. And I hope more developers could make full use of Vert.x to build their applications rapidly and concisely. So it is necessary to implement a series of applications using various part of the Vert.x toolkit to demonstrate the ability to build many kinds of applications.</p> <p>My goal is to implement some different applications using Vert.x and write detailed documents(both in English and Simplified Chinese) as guideline for the newcomer to Vert.x in order to help them understand the foundations of a vert.x application rapidly and then build complex applications. As for the newcomers who are from other frameworks, like Spring MVC or Spring Boot, I can also give a document for them using analogy to help them get used to Vert.x rapidly.</p>
Mentors: Student: ricardohmon
<p>Vert.x is a powerful framework to build polyglot applications based on the Java Virtual Machine. It is very suitable for projects developed following the DevOps approach. In this project, several demos will be implemented which will show how such a DevOps environment can be set up by using third-party tools. The common DevOps environment will include: setting up log aggregators (Graylog and Heka), use application monitors (New Relic and Netflix Servo), use of deployment recipes (Chef and Ansible), and lastly, configuring a complete continuous delivery pipeline based on Jenkins. All implemented examples will be accompanied by the corresponding documentation and guidelines.</p>