In this blog I’ll summarize the four weeks during the Community Bonding Period of GSoC 2016 :)

Week 1

The stuff of the first week:

  • Make contact with my mentors
  • Set up development environment
  • Do more research on my project
  • Read more documents and articles about Vert.x

Week 2

  • Discuss with mentors to refine my summer timeline and prepare a good project plan
  • Translate the document of Vert.x - From zero to (micro)-hero Microservice Lab into Chinese(a wonderful lab!)
  • Learn more about various components of Vert.x
  • Work on Vert.x Blueprint - Todo Backend, use multiple persistence

Week 3

Objectives

  • Refine project plan
  • Work on the English document of Vert.x Blueprint - Todo Backend
  • Refine the code and document of Vert.x Blueprint - Todo Backend
  • Learn more about EventBus and Vert.x Service Proxy
  • Design the structure of Vert.x Blueprint - Kue
  • Initial structure of Vert.x Blueprint - Kue

Issues

  • I viewed the code of Kue (Node.js version) and find it weird. Maybe I could write a Kue class referring to the encapsulation of KueVerticle. Every components of the Kue could use EventBus to interact with each other.

Week 4

Objectives

In this week, I’m planning to do the following stuff:

  • Finish Chinese version document of Todo Backend
  • Work on the Vert.x Blueprint - Kue (Initial implementation)
  • Learn from Kue’s design

Issues

  • Solved: How to use Vert.x Codegen in Gradle (for the lack of document)

Achievement

  • Learned something about Kue’s design
  • Refactored some of Vert.x Blueprint - Todo Backend code
    • Use @DataObject annotation to generate converter
    • Use Docker Compose to link two containers
    • Use Vert.x Launcher and read configure from json file
    • Resolve the id issue using incremental id (like auto_incr in db)
    • Remove redundant code
    • Update some part of documents

The Community Bonding Period is ending and the code period will be coming~ Exciting! Wish an amazing code summer with Vert.x!