Past Meetup

Go Meetup CRAFT edition

This Meetup is past

79 people went

Location image of event venue

Details

The famous CRAFT Conference takes place between 8-11 May and the Go Budapest meetup comes with a special CRAFT Edition (again). ⚙️ 🔧

📍 Location: Prezi workshop room

Speakers & topics

- Mark Bates: A Tasty Treat For All Your Database Needs - Pop is a database agnostic package makes it easy to do CRUD operations, run migrations, and build/execute queries. Is Pop an ORM? I’ll leave that up to you, the reader, to decide.
- Viktor Farcic: Can we remove humans from the process and make a system that is self-sufficient? The goal of this talk is to try to outline the steps required for a design of a self-adapting and self-healing system that will continue operating efficiently even when we are on vacations.

--

Let me introduce our first speaker, Mark Bates.

Mark is a full stack web developer with over 18 years of experience in building high quality scalable applications for companies such as Apple, USA Today, Klarna, and Palm. He wrote three books, "Distributed Programming with Ruby", "Programming in CoffeeScript", and "Conquering the Command Line". Mark is a regular speaker at conferences around the world, leads user groups such as Boston Ruby and Boston Golang, and helps organizing conferences such as GothamGo and GopherCon.

Mark is the co-founder of PaperCall.io, a platform for connecting technical events with high quality content and speakers. Mark is also a partner at Gopher Guides, the industry leader for Go training and conferences.

In his spare time Mark leads development of the Go web framework Buffalo.
https://github.com/markbates

❗️ Also, I would like to empower you to check his Advanced Go Workshop on Craft Conf. Tickets are still available
https://craft-conf.com/speaker/MarkBates

--

Our second spear is Viktor Farcic.

About his topic

What do we expect from a modern cluster? If a replica fails, it should be brought back up (rescheduled). If a node goes down all the services that were running inside it should be distributed among healthy nodes. Those tasks are easy to accomplish. Schedulers (Swarm, Kubernetes, Mesos/Marathon, and so on) are already doing those things for us. Many solutions provide self-healing by making sure that the system is (almost) always in the desired state.

The problem with self-healing is that it does not take into the account constant changes. The number of requests is continuously changing, errors are created, network bandwidth is fluctuating, and so on. A cluster, and services inside it, is like a living body that needs to adapt to changes continuously. Services need to be scaled and de-scaled, nodes need to be created and added to the cluster only to be removed soon after. We call that process adaptation. Even that is not the problem in itself, as long as we have an army of operators that will monitor the system and do reactive and preventive actions.

How about converting adaptation into self-adaptation? Can we remove humans from the process and make a system that is self-sufficient?

The goal of this talk is to try to outline the steps required for a design of a self-adapting and self-healing system that will continue operating efficiently even when we are on vacations.

❗️ Also, I would like to empower you to check his Building A Self-Sufficient System workshop on Craft Conf. Tickets are still available
https://craft-conf.com/speaker/ViktorFarcic