JavaOne 2016 short highlights
Download as PPTX, PDF0 likes1,175 views
JavaOne 2016 was a major Java community event held in San Francisco from September 18-22, coinciding with Oracle OpenWorld, attracting around 50,000 participants, including several hundreds from Finland. Key topics discussed included updates on Java EE 8, the roadmap for Java EE 9, and advancements in microservices support. The event also featured resources for further learning, including links to videos and GitHub repositories relevant to the Java ecosystem.
JavaOne 2016 short highlights
- 3. MITÄ, MISSÄ? › Java yhteisön kokoontuminen San Franciscossa, 18.-22.9.2016 › Yhdenaikaisesti Orace Openworld kanssa, yhteensä n. 50 000 osallistujaa › Suomesta muutamia satoja › Suurin Java-tapahtuma, suurimmat julkistukset ja tiekartat tulevaisuuteen › Piilaakson pöhinät ja näppituntumat
- 5. JAVA 9 – AND BEYOND public class Point(int x, int y) { } var url = new URL("https://sitepoint.com/java"); var connection = url.openConnection();
- 6. Copyright*©*2016,*Oracle*and/or*its*affiliates.*All*rights*reserved.**|* 38* Engage"Java"EE"Community" • Feedback*through*Survey* • Launch*Java*EE*Next*JSRs* 2016" Java"EE"8"" • Specs,*RI,*TCK*complete** • IniHal*microservices*support** • Define*Java*EE*9** • Early*access*implementaHon* of*Java*EE*9** Java"EE"9" • Specs,*RI,*TCK*complete* • Modular*Java*EE*runHme** • Enhanced*microservices* support** Java*EE*Roadmap* 2017" 2018"
- 8. JAVA EE 9Recent"Java"EE"7"compa. bility"updates:"Congratula. ons!"" ! ! ! ! Programming"Model" ! State" ! Eventual"Consistency" ! ! ! Resiliency" ! ! Serverless" ! ! ! Security"! ! ! Packaging" ! ! Mul. tenancy" ! ! Config u ra. on" ! Key"Value/Doc"Store"
- 9. SPOCK FTW class Spock_RouteIT extends Specification { def 'should succeed on basic call'() { def client = new RESTClient('http://localhost:8181','application/json') when: 'we attempt to call GET ALL NEW ROUTES endpoint' def resp = client.get(path: '/api/routes/find/all/new') then: 'we should get non-zero response with http status 200 OK' with (resp) { status == 200 !data.isEmpty() data.size() >= 0 } } }
- 11. DOCKER Stack, Swarm, Swarm of Stacks? 1.13
- 12. KUBERNETES Pod, Service Performance benchmarks: 1000-node clusters, 30 containers per node, 30000 containers Google: Two billion containers a week 3300 containers up every second
- 14. OVEROPS
- 15. JENKINS 2 & CLOUDBEES & PIPELINE https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
- 16. JFROG+ XRAY
- 18. WILDFLY SWARM
- 21. LINXXX › Ennen muuta, lue blogisarja dev.solita.fi, etenkin: • http://dev.solita.fi/2016/09/26/JavaOne-executive-summary.html › Videoituja • https://www.youtube.com/playlist?list=PLPIzp- E1msrYicmovyeuOABO4HxVPlhEA
- 22. LINXXX › Github tärppejä • https://github.com/docker/labs • https://github.com/arun-gupta • https://github.com/AdamBien • https://github.com/microprofile • https://github.com/cescoffier • https://github.com/wildfly-swarm • https://github.com/kenfinnigan • https://github.com/chanezon
Editor's Notes
- #16: Today, IMO there is little reason to use Job DSL because Pipeline is the Jenkins-supported mechanism for scripting Jenkins pipelines and it has met or surpassed much of the functionality of Job DSL. New plugins are being developed natively for Pipeline, and those that don't are being encouraged by Jenkins developers to integrate with Pipeline. And Pipeline has several advantages: There is no need to "seed" jobs using Pipeline as there is with Job DSL since the Pipeline is the job itself. With Job DSL, it's just a script that creates other jobs. With Pipeline, you have features such as a parameterized manual input step, allowing you specify logic midstream within the pipeline The logic that can be included in a Job DSL is limited to creating the jobs themselves; whereas with Pipeline you can include logic directly inside the job. Job DSL is simply much more difficult to create a basic delivery pipeline using, for example, the Build Pipeline Plugin; using Pipeline your file will be smaller and syntax shorter. And if you're using Job DSL to create Pipeline jobs, I haven't seen a major value for that anymore given the templating features available out-of-the-box with Jenkins Pipeline.
- #19: https://wildfly-swarm.gitbooks.io/wildfly-swarm-users-guide/content/getting-started/tooling/maven-plugin.html