Trifork Blog

GOTO Nights Amsterdam, Join & Learn!

March 8th, 2016 by

As an introduction to the GOTO Conference in June, we organize a monthly meetup to introduce you to the topics of the conference. These meetups are called GOTO Nights and are totally free to attend and food and drinks are included.

At the start of the GOTO season we gather together to decide which topics are interesting for developers to learn more about. For these topics we try to find the best speakers for the conference and for the GOTO Nights.

The tracks of GOTO Amsterdam 2016 are:

Connected Worlds: How did the IoT progress from both a conceptual as a practical standpoint?
Data: This track is all about collecting, mining and eventually striking gold!
JavaScript: This track will show you the current state of JS world, both in terms of frameworks, but also on a more “universal” level.
Legacy to Microservices: This track is about getting you on track again.
Lightning Talks: A series of 15-minutes talks submitted via a CfP.
Philosophy: How software impacts your life and how your life impacts software.
Post-Agile: This is about building the right product, releasing to production instead of releasing to the internal organization.
Security & Rugged: We need an approach to security in the context of human factors, adversary motivations & social impact.
Spring++: The latest & greatest of the features you have all wondered about.

On previous GOTO Nights we introduced the public already to the Spring++, Microservices, Data and Post-agile track. But we are not done yet. We have four GOTO Nights coming up until the conference, 13-15th of June.

10th of March: Stream Processing with Apache Flink and Mining Github

“Mining GitHub for Fun & Profit!” by Georgios Gousios (Radboud University Nijmegen)
With over 30 million repositories and 10 million users, GitHub is currently the largest code hosting site in the world. Software engineering researchers have been drawn to GitHub due to this popularity, as well as its integrated social features and the metadata that can be accessed through its API. To make research with GitHub data approachable, we created the GHTorrent project, a scalable, off-line mirror of all data offered through the GitHub API. In our talk, we describe how we setup GHTorrent, how we build a community around it, what types of research it has been used for and how Microsoft uses it to get insights from their OSS projects.

“Stream Processing with Apache Flink” by Robert Metzger” (Apache Flink and Data Artisians)
Data streaming is gaining popularity, as more and more organizations are realizing that the nature of their data production is continuous and unbounded, and can be better served with a streaming architecture. Streaming architectures promise decreased latency from signal to decision, a radically simplified data infrastructure architecture, and the ability to cope with new data that is generated continuously. Apache Flink is a full-featured true stream processing framework with:

  • Easy to use Java- and Scala-embedded APIs that make stream analytics easy, yet provide powerful tools to deal with time and uncertainty
  • Throughput close to a million of events per second per core
  • Latencies as low as the millisecond range
  • Full support for event time and out of order arrivals with flexible windows, watermarks, and triggers
  • Exactly-once consistency guarantees, and the ability to realize distributed transactional data movement between systems (e.g., between Kafka and HDFS)
  • Ease of configuration and separation between application logic and fault tolerance via a novel asynchronous heckpointing algorithm
  • No single point of failure
  • Integration with popular open source infrastructure (e.g., Hadoop, HBase, Kafka, Cascading, Elasticsearch, …)
  • Batch processing as a special case of stream processing, including dedicated libraries for machine learning and graph processing, managed memory on-, and off-heap, and query optimization

Flink is used in several companies, including at ResearchGate, Bouygues Telecom, the Otto Group, and Capital One, and has a large and active developer community of well over 140 contributors. In this talk, we provide an overview of the system internals and its streaming-first philosophy, as well as the programming APIs.

29th of March: What’s happening with the Elastic Stack? @FD Med

“Driving personalised news with Elasticsearch Percolators”, by Jeroen Snoeij (FD Mediagroep)
At FD Mediagroep we started using Elasticsearch for personalisation and searching through our archive of articles (since 1985). Since the introduction of the ‘my news’ section at, where users can build their own news page, we needed a way to bring this to our customers attention. We started using percolator queries in Elasticsearch to do exactly that. In this talk I will elaborate on what percolator queries are, how you can use them and how we use percolator queries at FD Mediagroep.

“Service Monitoring using Kibana, the ANWB case” by Patrick Kik (Trifork)
With over 3.000 car breakdowns a day ANWB needs to be highly efficient in handling their service calls. In this session Patrick will demonstrate how their Axon based event-driven architecture allows ANWB to gather valuable data insights with Elasticsearch and Kibana. These insights help ANWB to increase customer satisfaction by analyzing data for continuous process improvements.

“What’s happening with the Elastic Stack”, by Christoph Wurm (Elastic)
Recap of Elastic{ON} 2016
Christoph will tell about the expriences at Elastic{ON}16 with company and product highlights from the past year as well as what to expect with the upcoming 5.0 release. You’ll hear about updates coming to the Elastic Stack, learn about what the heck a Pack is, and see some awesome live demos of the Graph API.

13th of April: Implementing Infrastructure as Code

“Cloud Native Applications and Post-DevOps” by Pini Reznik (Container Solutions)
In the last few years DevOps was instrumental in starting the movement towards programmable infrastructure. Infrastructure that can be defined as the part of the normal development process and become a part of the application’s main codebase. But does DevOps gives us enough to address all the challenges related to the containers, microservices and all the developments in the cloud world?

In this talk I will argue that DevOps is just an intermediate step towards building cloud native applications. I will also show ideas for the future of the cloud that we are developing together with Cisco and other partners during our work on and

“Implementing Infrastructure as Code” by Kief Morris (Writer, ThoughtWorks)
Infrastructure as Code is a radically different way of working for many infrastructure teams, and for application teams. Users are used to raising tickets, sending emails, or coming around to the desks of infrastructure people to ask for things to be done. Infrastructure people are used to carrying out work by following checklists and running scripts. Managers are used to having detailed designs and project plans for major work, and change request forms and change review boards to handle smaller tasks.

Infrastructure as Code is very different. Infrastructure is defined in files in source control. Change management pipelines – like application deployment pipelines – propagate changes, automatically integrating and testing changes before they are pushed into production. The end result of this is that it’s possible to have much more rigorous control and assurance of infrastructure implementation and changes, with much less planning and ceremony. This talk aims to describe the moving parts of a typical organisation using Infrastructure as Code. Moving beyond the general patterns, to looking at exactly how changes are implemented and rolled out.

12th of May: Pragmatic Microservices

“Pragmatic Microservices” by Randy Shoup
One of the most powerful trends in software today is building large systems out of composable microservices. Many large-scale web companies have migrated over time to this architecture – and for good reason. But, as with any powerful technique, microservices come with their own brand of tradeoffs, and it is important to be aware of them before deciding whether they are appropriate in any particular case. They are not for every scale of problem, for every stage of company, or for every team.

This session takes a pragmatic approach to microservices, and compares them to the alternatives at different stages of company evolution. Using examples both from Google and eBay as well as from smaller organizations, it makes practical suggestions about whether, when, and how an organization should consider adopting a microservices architecture. Assuming microservices are the appropriate choice, it outlines an experience-based, incremental approach to making a successful rearchitecture to microservices.

Comments are closed.