In this webinar, Sven Peters @svenpet shared some thoughts about git workflows used at Atlassian. Continue reading Git Branching for Agile teams
Shaping the future of web development
Conference given by Lars Bak at Devoxx 2013.
Nowadays, an ever growing part of the population don’t even bother to start any other application than a browser. More and more applications are web applications.
An obstacle to web applications is the development productivity.
Practical RESTful persistence
EclipseLink provides a JPA-RS implementation. Let’s see what hides behind this.
The use case is a web application with the main logic inside the browser and a backend providing only persistency. We want to provide a REST API to that persistence. Continue reading Practical RESTful persistence by @shaunmsmith at #devoxx
Java 8 and beyond
Keynote performed at Devoxx 2013 by Mark Reinhold and Brian Goetz
Java exists for 18 years. Nothing can stay so long in the field without evolving.
One of the latest evolution in computer science is multiplication of cores and pipelines in processor.
For that reason it is intersting to look at problems from a perspective where everything is splitted in parallel data flows which split and split and split until complex problems resolve themselves as a multitude of simple parallel calculation.
To support that perspective, closures were added.
Fault tolerance made easy
Given by Uwe Friedrichsen at Devoxx 2013.
It describes a series of patterns applicable to vast majority of applications in order to support a user-friendly degradation of functionalities when a resource becomes unavailable or that the load becomes too high to cope with every request in a satisfactory way.
For once, this article is not about a conference but about some issues I thought about recently.
The context is a training session I give in my company. In that training session, I use a web app to illustrate some points and let the attendees perform some exercises. The web app project uses maven, spring-mvc and multiple databases (mysql and hsqldb) for different purposes (local playing, local integration tests, CI integration tests and “production”).
Those different purposes have different needs. Ideally, I would like to have something like:
- local playing –> local mysql database
- local integration tests –> hsqldb in-memory database
- CI integration tests –> dedicated mysql database running on the CI server
- “production” –> dedicated mysql database running on the “production” server
To update schema updates, I use liquibase. I would like to run it in update mode on environments 1, 2 and 4 and in drop-and-create mode on environment 3.
I know a lot of different solutions that can achieve this situation, but the solution must be neat (it’s a beginner training application and thus shouldn’t attract the focus on themes I don’t want to talk about). Currently, I still haven’t found THE perfect solution. So I’ll describe the ones I’ve already tried with some kind of success in coming articles. Feel free to propose anything in comment. I’ll be glad to investigate your propositions.
Now that I am a little rested from three frantic days in Antwerpen, I’ll start to structure my notes and write summaries about presentations I attended at Devoxx 2012.
Once again a big thanks to Stephan Jansens and his team. You rocks!