GOTO Amsterdam (June 17-19, 2015) is a vendor independent international software development conference with more that 50 top speakers and 500 attendees. The conference covers topics such as AngularJS, Disruption, Docker, Drones, Elasticsearch, Hadoop, Microservices & Scrum.
Jettro Coenradie, TweetFellow at Luminis
Biography: Jettro Coenradie
Jettro Coenradie is the Fellow at Luminis Amsterdam. He has been delivering applications for over 15 years.
In these years Jettro has learned the importance of a close connection between development and operations. Therefore he is a strong believer in the devops movement. One type of handover from development to operations is documentation, but the best one is good logs.
Jettro likes to try out new stuff. That is why he recently got his motorcycle drivers license. On a motor bike you tend to explore different routes to get the best our of your bike and have fun while doing the thing you need to do, get from A to B. When exploring new technologies he also likes to explore new routes to find better and more interesting ways to accomplish his goal.
Jettro rides an all-terrain bike, he does not like riding the same ground over and over again. The same is valid for his technical interest, he knows about backend (elasticsearch, mongodb, spring data, spring integration) as well as front-end (AngularJS, Sass, Less) and mobile development (iOS, Sencha touch). Recently Jettro started experimenting with home automation using raspberry pi, Arduino and Zigbee.
Twitter: @jettroCoenradie
Presentation: TweetOrganizing Work
Maintaining your Elasticsearch Indexes / 11:30 - 11:45
Some years ago, I was facing multiple projects with search challenges like "we need more options like synonyms, fuzzy search and facets", "our search engine is to slow" and "I cannot find what I am looking for". I got to know elasticsearch and by using elasticsearch I was able to create solutions for these challenges. While doing these projects I noticed doing some things over and over again. An example: you have to deal with the indexes your create, changes in the mapping, the number of shards. This occurs in development and in production. Another example: after importing some data, you want to check what is in your index. Can I execute the queries and filters I need and obtain the results I want?
Based on these experiences I first created some code to copy-paste from project to project and I created an AngularJS based gui to play with your data. Later on I added tools like: "where are my shards" to locate shards in your cluster and "Snapshots" to create and restore snapshots. The next step was to create a java based maintenance tool to maintain your indexes, set some cluster wide properties and manage the snapshots of your data.
In this talk I will give you the most important tips you want to know as an elasticsearch developer. I will show of the some tools I use and code I re-use in every project.
Working with what you got: Making the Best of Legacy Code / 11:50 - 12:05
In an ideal situation, a developer will work with either a blank slate or well-organized and succinctly-documented code, but in actuality that's rarely the case. In this talk, we'll briefly discuss common problems and frustrations with legacy code, demonstrate how it parallels with problems in legacy in other departments, and discuss how to reduce friction for others working with our own legacies.
by Nicollette Lui & Laurel Hechanova
Document Database Schema Design / 12:10 - 12:25
This talk is a short introduction of different schema design and patterns that one can apply on their application to match their use cases and MongoDB. We will briefly discuss the decision to use a specific design according to the rules of usage, data life cycle, query richness and write / read ratios.