We’re slicing and dicing systems into ever-shrinking pieces, from microservices to serverless functions, that should be reactive and event-driven. End-to-end processes now often require the integration of multiple components — but of course, without coupling them too tightly. In an e-commerce company, for example, a “customer order” might involve different services for payments, inventory, shipping, and more. I see many companies slicing up their core business processes in the pursuit of modern architectures and running into unanticipated challenges along the way.

This talk will foster your understanding of how (business) processes can generally be implemented and monitored. I will compare different approaches, from batches over streaming, to workflow engines. You will understand the impact on agility and what is different in modern architectures, as well as learning about choreography and orchestration.

Of course, you will also see concrete examples and live coding using Java, Spring Boot and Camunda.

Many organisations believe to be betting on interoperability by choosing Kubernetes rather than, what they believe to be, a proprietary platform. However, this could be a trap that can easily lead to vendor lock-in. We need to learn from history to avoid repeating the same mistake again.

Every organization has at least a phalanx or two in the “Cloud,” and it is understandably changing the way we architect our systems. But your application portfolio is full of “heritage” systems that hail from the time before everything was a service. Not all of those applications will make it to the valley beyond, how do you grapple with your legacy portfolio?

In this talk, you will learn:

• How to evaluate your legacy applications
• How to take those heritage systems to the Cloud
• What 12 Factors means for you
• Where it makes sense to use microservices
• What tools and services you’ll need to add to your repertoire

Industry practices for node projects encourage the development of microservices. In order to keep the project secure you need to keep your dependencies up to date. The more frequently this happens, the easier the fixes are as you are not working through a years worth of release notes. This talk covers the practical details of using dependabot to keep the dependencies of a project up to date.

The set of projects that the team I took over had over 70 repositories of code. Dependabot had recently been enabled and we now faced a backlog of 360 PRs (and these do grow by upto 70 a day).

This is the story of what my team did to get this under control. It also covers how to make Snyk and Dependabot play well together (and explain what happens when they don't).

This is what happens when you enable continuous delivery with dependabot, and what you need to make that happen.

Event-driven, serverless architectures are a hot topic in today's cloud-native application development. To take full advantage of the serverless benefits of event-driven, your application needs to scale and react to those events instantly. It needs to be able to scale from zero to potentially thousands of instances. KEDA is an open-sourced component that provides event-driven autoscaling for your Kubernetes workloads.

KEDA works with any container, but to enable additional serverless capabilities within Kubernetes you can pair KEDA with the Azure Functions runtime. Don't get fooled by 'Azure' in the name. Azure Functions provides a programming model that can run anywhere: in a container running on-premises, fully managed in Azure, or on any Kubernetes cluster, and they can be written in many languages.

It allows application developers not to worry anymore about writing the code to connect, trigger, and pull from an event source like RabbitMQ, Kafka, or Azure Event Hubs. That's all handled for you. Please join me in this demo-filled session!

The microservice architecture is a key part of cloud native. An essential principle of the microservice architecture is loose coupling. If you ignore this principle and develop tightly coupled services the result will mostly likely be yet another "microservices failure story”. Your application will be brittle and have all of the disadvantages of both the monolithic and microservice architectures.

In this talk you will learn about the different kinds of coupling and how to design loosely coupled microservices. I describe how to minimize design time and increase the productivity of your DevOps teams. You will learn how to reduce runtime coupling and improve availability. I describe how to improve availability by minimizing the coupling caused by your infrastructure.

The adoption of CI/CD has automated the process of how DevOps teams build, test, and deliver software at rapid speeds and with high confidence. Although CI/CD platforms offer many benefits, in the attempt to make sophisticated pipelines, many teams run into the issue of “Pipeline Sprawl”. Pipeline sprawl makes it difficult for DevOps teams to identify and reuse common execution patterns which diminishes their ability to efficiently ship new code.

In this talk, Angel will discuss the common pain points associated with existing CI/CD platforms. The talk will pull in examples from his recent experience and conversations with DevOps teams from across the open source community, startups, and large enterprises. Attendees will learn technical strategies to develop optimized pipeline configurations and diminish potentially costly vendor-lock in.

In our quest to secure all the things, do we jump in too quickly? We'll use Istio and Linkerd as example service meshes, and look at the features we would expect from a service mesh. We'll dive into the day-1 experience with both Istio and Linkerd, and some advanced scenarios of using the service mesh. We'll compare this to border security with an app gateway, and compare and contrast the security features, complexities, and implementation costs. You'll leave with a concrete understanding of the benefits and tradeoffs you get when you pull in a service mesh, and be ready to justify the investment.

Continuous Integration and Continuous Delivery/Deployment (CI/CD) concepts are increasingly adopted by many technology organizations and teams. CI/CD enables teams to establish processes that increase velocity, collaboration and quality of their codebase. CI/CD enables developer & operations teams to break down unnecessary silos and gain a deeper knowledge of their respective arenas.

In this workshop the participants will be introduced to the basic fundamentals of Continuous Integration and Continuous Delivery/Deployment. Participants will learn the core principles of CI/CD and have the opportunity to reinforce what they’ve learned in a hands on workshop featuring the CircleCI platform. The workshop will demonstrate CI/CD build configuration, code commits, commit builds, code testing and packaging. The participants will leave with a hands-on experience and understanding of what it takes to CI/CD.

*Pre-requisites: *GitHub account, Docker Hub account (for deploying), and a code editor of choice

This free pre-conference workshop will be led by Angel Rivera and Zan Markan. You must be a registered attendee of CloudNative eXchange to attend this event.

Most tech teams will take an Agile approach to launching new products and services. Starting with a Minimal Viable Product (MVP), and releasing iteratively  — gathering feedback, testing assumptions and delivering value to customers more rapidly. For migration projects though, this often goes out the window. With teams looking for a “big bang” release once the new system reaches feature parity (an equivalent set of features and functionaries) with the existing system. Instead, a focus on Minimum Viable Migrations (MVMs) allows assumptions to be tested faster, teams to be focused and value to be delivered to customers more rapidly.

Key Takeaways: * How to structure Cloud Modernization * What's a good MVM * How Serverless technologies can simplify MVMs

Many say: "Microservices are small REST services". But the technology choice for microservices is much bigger: Asynchronous microservices with Kafka or Atom feeds and integration at UI level are just as possible as REST in various variations, e.g. with Kubernetes and the service mesh Istio. This talk provides an overview of these approaches and when to use them.

Links to examples at GitHub and documentation will also be provided so you can actually start working with them.

Join us for lessons learned in building two different cloud delivery ecosystems, one that leveraged a single vendor and another that combined tools to pursue ‘cloud agnostic’ and poly-cloud computing.

Microservices, and especially the event-driven variants, are at the very peak of the hype cycle and, according to some, on their way down. Meanwhile, a large number of success stories and failures have been shared about this architectural style. Allard Buijze explains how not to throw away the baby with the bathwater and end up reinventing the same concepts again a decade from now.

Allard zooms in on different aspects of microservices. You’ll discover the promises made and if microservices delivered, how the technology surrounding microservices evolved and impacted your decisions, and what it means to be event-driven. You’ll also explore different ways in which a system can benefit from events, from events as side effects to events being the root of all state. Along the way Allard examines how to be pragmatic about microservices and avoid some of the common pitfalls, helping you ensure that you get the promised benefits without the pain.

How nice would it be to be able to remember everyone’s name? What if you could just walk into a room and know everyone’s Twitter handle? Kubernetes is a great tool that is being used more and more for deploying applications, and it can also be used in the context of machine learning. In this talk, Joel will demonstrate how to use NodeJs, a touch of machine learning and a sprinkle of Kubernetes to recognize people in a crowd.

With a demo inspired by the series Black Mirror, attendees will learn how to use openly available tools to do face recognition with NodeJs and how to deploy multiple microservices to Kubernetes.

Antipatterns are like patterns, just more informative in that you first learn what the immediate bad solution is before you get a better solution. Alongside the retrospectives I have facilitated architecture reviews and there are a lot of similarities between these two activities. Both include a shared experience that needs to be reflected on, both include people with pride and shame in what has been created, and both are under the usual time and resource constraints. Join me for a sad and entertaining talk about how your architecture review sessions can improve based on all my mistakes.

Cloud Architect Lynn Langit moved to Minneapolis in 2020 and expected to make positive change applying various cloud technologies. As for many, the year 2020 brought a number of unexpected turns to her newly-native city. What role does Cloud Native tech have in recovery for a wounded city? With COVID, riots, a struggling economy and bitter political division impacting globally, are there considerations / lessons we can all apply?