Notes of JCConf 2017
Last updated
Was this helpful?
Last updated
Was this helpful?
This post is for memo of JCConf 2017, the meeting agenda can be referenced .
Dependency management V.S. classpath declaration (painful when projects grows big, can refer to the part of: )
Modularization for adaption to different runtime environments, such like a mobile device (can refer the part of: ).
Node.js style module descriptor (requires, exports, uses, provides...)
Jlink - Running your application with minimal load (can refer to the part of: ).
Jdeps - CLI for display dependencies between jars ().
This talk not only addresses on spring boot development but also great philosophy of software development.
Why microservice? Agility, Scalability (reliability also, of course).
Monolithic V.S. microservice is like: painting V.S. diorama
In most of the cases, the application includes web + data:
spring-boot-starter-web
spring-boot-starter-data-jpa
Test your app with spring test:
spring-boot-starter-test
Spring Cloud (microservice ready framework)
Message queue tool:
A beautiful say: "Start simple, not small."
What does "reactive" mean? Event-driven (take ideas from Node.js: Async, Non-blocking IO)
Reference:
The spirit of software developing: . (The debate about TDD is extremely the case.)
Using to create a porject workplace.
ORM tool selection:
Using (a service discovery server)