Spotkanie PJUG - Real life Clean Architecture and Top Java Performance Mistakes

Our next PolishJUG meeting is going to happen on 19th of May 2016 at 6:15 p.m.

We will have a pleasure to listen 2 presentations by Mattia Battiston on Architecture and by Andreas Grabner on Java Performance Mistakes.

Our sponsor, this time, is SKY (https://jobs.sky.com/).

http://photos2.meetupstatic.com/photos/event/6/4/9/c/600_449665756.jpeg

Thank you!

Mattia Battiston

Mattia is software developer with a great passion for continuous improvement. He works in London for Sky where he uses Kanban, Lean and Agile to help his team (and a few other ones) strive to improve.

Real life Clean Architecture

We like the architecture of our applications to revolve around the business logic, not around technical details (and especially not around the database).

In my team at Sky we use the Clean Architecture and it has given us a great deal of benefits: the business logic is explicit, we are free to change our technical decisions, the app is easy to test, working on it is faster and scalable, it’s hard to do the wrong thing, and many more.

But it comes with a cost, of course. In this talk I’ll tell you the story of our experience with Clean Architecture and give you some tips to get the most out of it.

Andreas Grabner

Andreas is a performance advocate who has been working in this field for the past fifteen years. Andreas helps organizations identify the real problems in their applications and then uses this knowledge to teach others how to avoid the problems by sharing engineering best practices. He was a developer, tester, and evangelist for Segue Software, builders of the Silk Testing product line. Later Andreas joined Dynatrace where, for the past eight years, he has helped organizations worldwide test applications, better understand the technologies behind their apps, and improve the entire development process. He shares his expertise on blog.dynatrace.com

Deep Dive into Top Java Performance Mistakes

Most performance problems in Java applications under load don’t require a large load test for diagnosis. The top problems in the last years all have to do with architectural issues such as excessive database access, allocating too many objects, bad connection pool handling, or badly deployed and configured frameworks. This presentation shows you several real-life use cases, the metrics to look at, and how to capture these metrics with your unit and integration tests. It uses free tools such as JMeter, JUnit, and Dynatrace to get this accomplished

As usual you need to be prepared for a lot of attractions including prizes, beer and pizza :)