Learn how to write code so beautiful, that it makes you want to frame it and put it on your wall. And there's more: it will be usable and maintainable.
I will tell you about:
Event-driven architecture allows you to observe, collect, analyze, and react dynamically to real-time events.
Since most of functionalities of our applications are reactions on some requests or situations it's worth to know advantages of event processing and event-driven architecture.
Ability to recognize events we have to react on make as more aware of the domain we have to work with. Including them into our applications makes our software more cohesive, granular and easier to understand, extend and modify.
During the talk you will learn what event processing is. What are the differences between event processing and event sourcing. I will describe major concepts of event-driven architecture and tell you how to design event processing applications.
The „game development” term is stereotypically associated with an image of programmers coding efficient engines, designers thinking about fluent gameplays, artists, animators and sound engineers working together to create stunning environments. Naturally, there’s a lot of truth in that. Nowadays, however, when publishing applications is getting easier and easier and the market is more competitive than ever, some other factors come into light and become essential.
Following the dynamic growth of public cloud idea, initially used mostly by business applications, the game developers seem to start noticing and using its power for their own purpose. It turns out that the available technologies and software development methods create a lot of new opportunities for both small, indie developers and game dev giants. Some game genres even seem to be highly dependent on different mechanisms implemented in cloud.
How exactly can you profit from using cloud, how to begin working with cloud to use it effectively throughout the process of developing, publishing and maintaining a game? The purpose of this speech is shedding some light on this subject with a little help of real world examples.
Let’s imagine startup where count of members grow from 1 to 100 in one year and technology stack grow in similar speed - more developers, more tools, more services, more environments - how to get all these things to work, be Agile and not get crazy? We will try to dig this topic and see advantages hidden in Infrastructure as Code, looking on benefits coming from CI/CD as Code, in wild microservices world.