Craig Walls
New England Software Symposium
Boston · Feb 27 - Mar 1, 2015
Author of 'Spring in Action' and 'Spring AI in Action'
Craig Walls is a Principal Engineer, Java Champion, Alexa Champion, and the author of Spring AI in Action, Spring in Action, and Build Talking Apps. He's a zealous promoter of the Spring Framework, speaking frequently at local user groups and conferences and writing about Spring. When he's not slinging code, Craig is planning his next trip to Disney World or Disneyland and spending as much time as he can with his wife, two daughters, 1 bird and 2 dogs.
Presentations
What's new in Spring?
It was over 10 years ago that Spring hit the scene and made a big impact in the enterprise Java development ecosystem. Now that Spring 4.2 is available (and Spring 5 on the way), there's a lot of new features and a lot that you may not know about yet.
Cloudy with a chance of Spring Boot
You wouldn't write your entire application in a single main() method or servlet. Nor would you develop an entire production-ready application in a single class. It's even unlikely that you'd cram everything into a single package.
Modularity helps us gain order in our code, breaking it into easily digestible, refactorable, pluggable, and testable chunks. Classes and methods are a form of modularity that we're all familiar with. But once the code is built, modularity goes away and we're left deploying a single WAR file.
Aside from being buzzword-compliant, Microservices are a means of defining entire systems from composable, but distinct deployment units gaining all of the benefits of finer-grained modularity. As it turns out, Spring is well-equipped as the platform on which we can build and deploy microservices.
Efficient Client-Server Communication with Differential Synchronization
In this session, we'll look at a technique known as Differential Synchronization, building on top of HTTP PATCH and JSON Patch to enable efficient two-way conversation between clients and the servers they deal with.
Reactor for Reactive Programming on the JVM
Cause and effect is a process that is generally missing from many of the applications we write. In a typically application, if a value needs to be calculated or some data needs to be moved from one part of the code to another, we call a method. Consequently, we find ourselves writing synchronous and highly-coupled code.
Reactive programming, on the other hand, allows you to develop code in as asynchronous streams of data, listening for data events and reacting to them asynchronously. Reactive code is generally cleaner, more concise, and involves less coupling.