Good news: Java build tools constantly getting better. From make to Ant, to Maven1 to Maven2, our builds are simpler, more reusable and more reproducible. Bad news: We aren't there yet. Current solutions are limited and limiting. The industry is looking for post-maven2 build alternatives, which preserve the benefits and overcomes the flaws of today's build tools. Gradle makes sounds of such an alternative. Gradle is Groovy-based build tool which combines the freedom of dynamic scripting language, the power of Ant and the conventions of Maven2. That's a better way to build. Gradle enables you to create declarative, maintainable, concise and highly-performing builds. During this session we'll show how.
Writing highly scalable, concurrent, fault-tolerant applications for the Java platform is hard. Akka, a next generation event-driven, scalable and fault-tolerant platform makes true scalability easy. Akka is implemented in Scala but allows applicative code to be written in either Java or Scala. Akka employs both Erlang-style actors concurrency model and STM (Software Transactional Memory). It makes it easy to expose actors remotely. It enables easy persistence on scalable storage engines such as Cassandra, MongoDB and Redis. It enables to supervise and provision services transparently; exposes a RESTful API; makes it easy to consume and expose services in a very flexible way via Camel; integrates with Spring, Guice, message queues and much more. In a very short time it has become the choice for a robust, scalable and easy to maintain server-side platform. In this session we will make a quick dive into Scala and see what makes it a very accessible and compelling language for the JVM. Then we'll see a few examples of Scala on the Akka platform
APPles, Oranges, And NoSQL: A Foray Into The Persistence Jungle
Too many different seemingly viable options -- the recent onslaught of non relational databases has created a dizzying array of alternatives that's difficult to pull into focus.
This session will provide you with a roadmap to guide you through the persistence jungle. Together, we will examine:
Avoid off label usage: Which NoSQL solutions are suitable for what purposes -- who should consider NoSQL, and who should go look someplace else?
Comparing apples to oranges: How do NoSQL databases measure up against relational databases for both transactional and analytical workloads, and how are RDBMSs being influenced by them
Not Only SQL: How can these different solutions be used to complement each other