Grails 3 includes a lot of features and functionality related to building RESTful services. These include an entirely new and more flexibile data binding system, runtime and compile time metaprogramming which greatly reduce the amount of code required in your RESTful services, a rich set of content negotiation tools and more.
10 years in the making and finally JSR-107 has been finalized. We now have a standardized Caching API for the Java Platform. And that's all ready for you to use in your Spring apps. But what does it really enable for you? What's with these optional features? No transaction support? How do you efficiently make use of this new API to solve real world problems in your application today? We'll look into how get you best started introducing caching into your Spring application to solve real world problems. And, as we explore the javax.cache API in much more details, we'll see how to push the specifications to its limits and... beyond. Whether implicitly through frameworks (like Spring and Hibernate), or explicitly (cache-aside, cache-through, ...). And how to abstract yourself from a given provider when you require more than what the specifications cover (e.g. transactional caches). We'll also cover some implementer specifics you might want to account for when choosing an implementation, especially if you plan to push the spec to the extreme, like when going distributed and caching terabytes of data.
In a world of the cloud, virtualization, containerization, microservices and nanoservices we talk about scaling up, scaling out, and decoupling our systems, but typically miss scaling down to an embedded platform.
At the same time that we have moved away from heavy monolithic web containers, we've seen a rise of powerful low cost embedded Linux devices such as the RaspberryPi.
The web has evolved tremendously in the last decade. In this talk we will dive into the latest tools and techniques that make for a modern foundation for frontend engineering. We will start with bootstrapping with Yeoman, move into managing dependencies with bower, and finally how to automate best practices with Grunt and Gulp. We will discuss the pros and cons of modern ui toolkits like Zurb, Bootstrap, and SemanticUI and modern javascript frameworks like React, Angular, and Ember. We will highlight the latest in css frameworks, javascript frameworks, and why you should choose the right toolset for complex app or a single page app. When you leave this session you will be prepared to launch a modern web application in 2015.
Recorded at SpringOne2GX 2015
Speakers: Juergen Holler, Stephane Nicoll
Slides: http://www.slideshare.net/SpringCentral/modern-java-component-design-with-spring-framework-42
Spring's programming and configuration model has a strong design philosophy with respect to application components and configuration artifacts. Spring's annotation-based component story is fine-tuned for source code readability as well as consistency across an entire application's codebase. This session presents selected Spring Framework 4 component model highlights, with a focus on the upcoming Spring Framework 4.2 and…
Even if I pointed out that there are no general news in terms of Java EE 7 platform adoption in last week's blog post (since there is still no WebSphere Classic, WebLogic, JBoss EAP or even TomEE with full EE 7 support), the two existing open-source EE 7 platform servers - namely, GlassFish and WildFly - made some fine progress in the meantime:
There's a GlassFish 4.1.1 release now, with many sub-project updates - including Tyrus for its WebSocket support.
And the WildFly team rushes from major release to major release, arriving at WildFly 10 GA very soon now. The underlying Undertow web server reached 1.3 GA just a few days ago.
A reminder: Every time somebody shows you a survey result with a Java EE 7 usage column, in particular when talking about production usage, double-check what they actually asked for. Does Hibernate 4.3 usage count as Java EE 7, just because it's JPA 2.1 (EE 7 level but run standalone)? Does Tomcat 8 usage count as Java EE 7, just because it's Servlet 3.1? And of course, does running a Spring application with any such individual providers count as EE 7?
Take such statistics with a big grain of salt: They typically do not ask for "native Java EE 7 platform usage" but are being presented that way eventually. Why is it a safe assumption that they did not ask for full Java EE 7 platform usage in production? Well, remember my blog post from back in June, which is still as valid in late 2015. In the meantime, the only real news is that there is no news since IBM released their EE 7 support in WebSphere's Liberty Profile. All in all, responders to such survey…
Turkcell launched a personal cloud storage service few years ago. Adding new business features was costly in terms of time and budget on the legacy solution. The user experience needed to be improved. Finally, it was decided to build a new solution where Spring Boot and Spring Framework projects play crucial role as the backbone. The project was completed just in 6 months starting from scratch. The solution was built on top of Spring Boot and many Spring IO Platform projects, allowing the development team focus on business logic instead of configuration & integration details. The project has been divided into deployable modules (API, backend, migration, test automation) accessing micro services that are responsible for one task only. Join Erdem for a review of the migration effort and new architecture - all enabled by Spring Boot.
So you have decided to build an application using Spring Boot? Sooner or later, something will go wrong. It does not matter how experienced we are. How will Spring Boot help us figure out what went wrong and fix things? This talk introduces lots of tools to help us debug and manage "bootiful" apps. You will learn how to use Boot's autoconfiguration report, override Boot's settings & beans, create custom metrics/health checks/app info, and create custom JMX info & custom CRaSH commands.