event-driven architecture
Showing 11 out of 11 results
Expert Talk: Cloud Native and Serverless
Should everyone move to the cloud? Are all event-driven architectures serverless or is it the other way around? Join the two experts, Matt Turner, software engineer at Tetrate, and Eric Johnson, principal developer for serverless at AWS, to discover if you should make that journey and how does that journey look like. Understand the power of these technologies together with some useful tips & tricks about testing and the BEAM languages.
Moving Beyond Monoliths and Microservices
Microservices have become more than a buzzword and are now viable alternatives to monoliths, which makes understanding why and how they should be used more important than ever. Thinking strategically about software architecture has to be the cornerstone of any software development. Vaughn Vernon, author of “Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture” (Addison-Wesley Signature Series (Vernon)), and James Higginbotham, author of “Principles of Web API Design”, discuss purposeful architecture, why events matter in software and much more.
Building Evolutionary Architectures
"Discover a fresh perspective on software architecture and time. Stay ahead of the game by protecting architectural characteristics and adopting new frameworks.
Somm Lagom - Building Systems that age like wine
Keeping up with the pace of change in emerging technology is an ever present challenge for enterprises. Trying to build systems that age and evolve gracefully over time is not a small task. We are all familiar with frameworks that help us implement architectural patterns, especially application architecture. In this session we will investigate Lagom, a new class of framework designed for system building, specifically, Reactive Systems. I will discuss common challenges I’ve encountered implementing large scale Reactive Systems and review Lagom features designed to address these challenges head-on. Though an investigation of this Scala-based framework, we will learn how system-building frameworks help Enterprise Architecture to rise to the challenge of aging like wine. **prerequisite attendee experience level:** advanced
Building Microservices Systems with the Axon Platform
Axon Framework is a well-established open source framework for writing CQRS, event-sourcing and DDD based applications in Java. It has been around for 8 years and is used in business applications around the globe, with the financial services industry proving to be a sweet spot. On 18 October, Axon 4 has been released. Starting from this release, Axon is a platform, consisting of the open source Axon Framework and the open source Axon Server. The platform offers a unique, scalable way to build microservices. It allows developers to focus on functionality, with things like correct routing of messages being handles by the platform. In this session, we'll look at the Axon platform in detail, and see it in action, including some live coding.
50.000 Orange Stickies Later
It started like a tool for discovering Aggregates, then became a teaching tool for the DDD-illiterates. Now EventStorming is a platform for collaborative modelling whose depth spans from business and organizational design to implementation level software design. In this talk you’ll understand how different recipes can be leveraged for different goals and different audiences. And how those weird human brains behave, when we take them in unexplored places.
Modular Monoliths
If you want evidence that the software development industry is susceptible to fashion, just go and take a look at all of the hype around microservices. It's everywhere! For some people microservices is "the next big thing", whereas for others it's simply a lightweight evolution of the big service-oriented architectures that we saw 10 years ago "done right". Microservices is by no means a silver bullet though, and the design thinking required to create a good microservices architecture is the same as that needed to create a well structured monolith. And this begs the question that if you can’t build a well-structured monolith, what makes you think microservices is the answer? **Prerequisite attendee experience level:** professional
The World after Microservice Migration with Service Mesh and Contract Testing
Refactoring complex legacy monoliths into microservices is on the agenda of many tech companies of today. Once the migration is over, however, one quickly learns that the complexity simply spills over from the "dev" to the "ops" side. Many new infrastructural questions arise. For example, how do we maintain stability in a dynamic ecosystem of microservices? How do we recover from communication failures or identify performance bottlenecks in call graphs? During the refactoring, it's important for legacy clients that the APIs behave in exactly the same way as before, even exhibiting the same quirks and "features". Later, and especially with continuous deployment practices in place, developers have to be confident that changes in a microservice do not break its consumers. In the first part of the talk we will discuss the concept of a service mesh, a dedicated infrastructure layer for tackling the inter-service communication. We will analyze existing solutions, such as linkerd and Istio, and cover practical aspects of installing a service mesh on both AWS ECS (with the help of Consul) and Kubernetes. In the second part we will discuss consumer-driven contract testing. We will go through the process of creating contracts for existing systems but also see how to build new services by starting from a contract definition. And since defining the contracts isn't enough, we will show a way of integrating them in build pipelines. **Prerequisite attendee experience level:** beginner
Event-based Architecture and Implementations with Kafka and Atom
Events provide many benefits - among them strong decoupling. Or do they? This presentation shows what has to be considered when designing an event-based architecture and how to really gain the expected benefits. Implementations with technologies such as Kafka and Atom are also covered.
The 7 Quests of Resilient Software Design
Resilient software design is around for some years meanwhile. Still, there seems to be a mismatch between popularity and progress - while patterns and libraries are quite well known for a while, only little progress in terms of creating better robust applications seems to be made. In this session we will examine the probably biggest obstacles and pitfalls on our way towards creating resilient systems. You will learn what they are, how you identify them and what you can do about it. After all, it is still a long way to become a resilient software designer ...
Event-Driven Microservices - not (just) about Events!
"Events" have recently been given a lot of attention as a very powerful means of communication between components. They pop up almost everywhere in different shapes and forms, and for different reasons. Unfortunately, they often completely miss their purpose, and instead of decoupling components, they subtly introduce an implicit coupling in logic. The distributed big ball of mud is born. Throwing more technologies at it won't solve the problem, all it will do is simply introduce a new layer of mud on top of the old. In this session, I will take a few steps back and look at three reasons why components need to communicate. I will demonstrate that by considering the reason of the communication, you can select suitable routing patterns, choose an appropriate protocol and technology to transport each type, and end up with proper decoupling of components. This decoupling means that it doesn't matter anymore whether the messages are handled in the same process as the sender, on different hosts or even in different data centers altogether. This so-called location transparency then becomes a big enabler for building evolutionary "message-driven" microservices.
