Spring Framework 5 is here, along with Spring Security 5, Spring Data Kay and Spring Boot 2! One of the most exciting introductions in this generation of Spring is reactive programming, building on Project Reactor to support message-driven, elastic, resilient and responsive services. The new Spring WebFlux framework integrates an MVC-like component model for reactive processing as well as functional reactive endpoints. We'll look at the new Netty-based WebFlux runtime and also discuss the use of reactive programming patterns with existing technologies such as Spring MVC.
About Juergen and Josh:
Juergen Hoeller is co-founder of the Spring Framework open source project and has been serving as the project lead and release manager for the core framework since 2003. Juergen is an experienced software architect and consultant with outstanding expertise in code organization, transaction management and enterprise messaging.
Josh is the Spring Developer Advocate at Pivotal. Josh is a Java Champion, author of 5 books (including O'Reilly's upcoming 'Cloud Native Java: Designing Resilient Systems with Spring Boot, Spring Cloud, and Cloud Foundry') and 3 best-selling video trainings (including 'Building Microservices with Spring Boot Livelessons' w/ Phil Webb), and an open-source contributor (Spring Boot, Spring Integration, Spring Cloud, Activiti and Vaadin)
All successful products focus on the user. As a developer, you are your software's final UX guardian. It is in your power to make or break its user experience. Therefore, it is your responsibility to make sure things don't go sideways. Thankfully, every developer is an API designer, and every API designer is a UX expert. Here are the reasons why...
Holger Weissböck is Chief Design Officer at Dynatrace and has been with the company for 9 years. He is software developer, team lead and UX designer with experience in enterprise, framework, backend and game design and development. Otherwise, he loves good music, good food and old cars.
Electricity Comes from the Socket and IT Comes from the Cloud
“Serverless” and “Platform as a Service” (PaaS) are buzzwords being currently on everyone’s lips. But they also cause headache: How doing an internet without servers? Who is responsible for the IT infrastructure? Can we dare to go this way or are we at mercy of Microsoft, Amazon, Google and Co. with neck and crop? Rainer Stropek tries to give answers to these questions. He shows with live demos the state of the art in Serverless Computing with Microsoft Azure and how these products and concepts are used in modern application architectures. Rainer will also show us the reality behind the curtain und tell how the processes and tools at Microsoft look like. So maybe at the end we, as a developer team, need not care of servers anymore?
Rainer Stropek is co-founder and CEO of the company software architects and has been serving this role since 2008. At software architects Rainer and his team are developing the award-winning SaaS time tracking solution “time cockpit”. Previously, Rainer founded and led two IT consulting firms that worked in the area of developing software solution based on the Microsoft technology stack. Rainer is recognized as an expert concerning .NET development, software architecture and databases. He has written numerous books and articles on C#, database development, Microsoft Azure, XAML, and web development. Additionally he regularly speaks at conferences, workshops and trainings in Europe and the US. In 2010 Rainer has become one of the first MVPs for the Microsoft Windows Azure platform. In 2015, Rainer also became a Microsoft Regional Director. 2016, Rainer also got the MVP award for Visual Studio and Developer Technologies.
This talk will tell the story of how our backend architecture evolved over the last 8 years. It will give insights into how we gradually moved from 2 monolithic services with lots of design flaws to a modern microservice architecture using several database technologies. Pitfalls, mission-critical situations, major challenges, as well as technology and topology decisions will be explained in the process. Besides all the architectural topics, I will also talk about team structure and how our deployment changed over the years. Switching from departmental to agile feature teams also had an impact on how we now have to design our microservices. This switch forced us to rethink our deployment strategy completely. In the early days we rented our servers from a hosting company in Germany, then we bought our own servers and ran them in two different data centers. Our newest strategy is to switch from virtual servers to containers running in our on-premise OpenShift cluster. The level of detail in visually representing our architecture will increase throughout the presentation as we approach the present.
Simon started his professional life in chip design, but he has always loved software a little bit more. Not just because software is more agile than hardware development, but because tackling bigger problems at higher levels of abstraction is more appealing to him. This is also why he fell in love with Ruby as soon as he tried it out. In 2010, Runtastic gave him the opportunity to join as the 4th full time employee and work on the Rails web page and Ruby backend. Over the past few years, he helped to scale the technical system and the company’s development teams. On the way to his current Lead System Architect role, he was in charge of the backend development team for several years and was part of the project team to transition the development process from departmental to agile feature teams.
Overview of principles and load-shedding mechanisms in large-scale services and how they impact service management.
Acacio started his career at Google as SRE Manager for GMail in 2016. Then created many SRE teams, onboarded services with those teams and developed the processes to improve services. This work led to the genesis of several software engineering projects aimed at building services with built-in best practices for reliability and ease of service management (load-shedding, monitoring, software frameworks).
Making Security an integrated part of the Software Development Lifecycle
SDLC - How we can improve security in our development by making it an integrated part of the development process. Today we use a large variety of tools for improving our development experience and process. We have unit tests to make sure our code performs like we intend. Code reviews for sharing knowledge and catching bugs. We use automated deployment to ensure that what we build is what we deliver, and we can package this with containers. With all these things in our pipelines, we have a strong foundation for adding security to our development process without having to radically restructure how we work.
Have you seen a fire breathing dragon dual wield My little pony figurines? How about an IT Security employee with a burning passion for keeping users safe and security fun? Siren Hofvander delivers on the latter and strives for the former in her daily job as CSO for Min Doktor - responsible for the security of not only the patient data but also the service itself. She is an expert of embedded security and specialises in building security into the SDLC and firmly believes that security is a task for everyone, not just the hacker elite. She also heads up the Malmö based IT Security group SecuriTea and is an avid forum contributor.
Serverless technologies bring you to adopt event-driven architectures. I created “Serverless by Design”, an open source tool that can help you to quickly think, build and iterate on a visual representation of your project. First, it can map event-driven architectures to a network model, easy to edit and visualize. Services and functions are nodes of the network, and the interaction between services and functions (such as triggers, read/write access, and other integrations) are edges. Then, it can build the starting code of your app using AWS SAM templates, or the Serverless Framework. Finally, we’ll give an example on how to deploy an application globally, across multiple regions.
Danilo works with startups and companies of any size to support their innovation. In his role as Technical Evangelist at Amazon Web Services, he leverages his experience to help people bring their ideas to life, focusing on event-driven programming and serverless architectures, and on the technical and business impact of machine learning and edge computing. He is the author of AWS Lambda in Action from Manning.
Improving a product’s quality isn’t possible without the needed appreciation throughout every member of the team, but finding the right approach everybody is comfortable with isn’t easy. We learned, the right mindset is key for which we found a simple solution. For us adding Cucumber (BDD framework) to Nightwatch (Selenium) was the right step to create a testing environment which everybody can identify with, as now everyone can use the programming language he/she prefers. For the right workflow we introduced user stories, so that misunderstandings could be reduced.
Ekaterina Budnikov (SEO and QA Manager) works at shopping24 internet group - an e-commerce company in Hamburg. She focuses on improving shopping24’s User Experience and Software Quality throughout all product teams. Therefore she is eager to learn new stuff and to share her experience and learnings with others. For example by sharing her sketchnotes of conferences and other events she attended.
How do 1,500+ OpenStack developers from 150+ companies contribute to the same code? And how is it consumed in a way that it becomes part of a business solution? During this talk we'll cover CI/CD at scale and how to leverage those same principles and tools for a distribution, partners and customers following an upstream first approach. Open source projects like Software Factory and Distributed Continuous Integration aim to serve open source communities beyond OpenStack in the quest to building better software.
Maria focuses on strategy, execution, and delivery of innovative solutions for leading companies across multiple industries. In her role as Principal Product Manager for Red Hat OpenStack, she interacts with both technical and business leaders in the open source community. This includes technology partners, customers, and users. She also works on free and open source projects, driving their adoption and improvements from incubation to productization.
I've seen projects with shiny, new code render into unmaintainable big balls of mud within 2-3 years. Multiple times. But regardless of whether it's the code base as a whole that's rotten, or whether it's just the UI and User Experience that needs a major overhaul: the question on rewrite vs refactoring will come up sooner or later. Based on years of experience, and a plethora of bad decisions cumulating into epic failures, I'll share my experience on how to have a code base that stays maintainable - even after years. After this talk, you'll have more insight into whether you should refactor or rewrite, and how to do it right from now on.
Martin is Software Architect at Dynatrace, speaker at various events, occasional blogger, regular practitioner. Focusing on the human side of things.
Agile software delivery teams have to apply other methods than only testing to ensure the fast and robust delivery of an overall high quality product. Additionally, these methods need to be applied in the (changing) context of our work. This includes understanding the business value as much as the system architecture of the product. Once the environment is understood the team can apply methodologies like continuous integration/deployments to ensure a quick delivery of a robust product. As a result, on the one side the classic QA role is stretched far beyond managing tests and releases while on the other side entire software development teams need to step up, too. Finn argues that we need to embrace this change. Once we understand to view the big picture in software development teams, we can level up and focus on our core value: driving a quality culture.
Finn is Product Quality Specialist at ThoughtWorks and cares about high quality software from his heart. He is an analyst. Sometimes he analyses client business needs, sometimes teams and their processes and sometimes software. Finn loves being the team driver towards building a high quality product. He strongly believes in the benefits of truly agile environments to achieve this goal. In his previous life he was a physicist: Finn was analysing how to build transistors and hard drives out of single molecules.
Our DevOps journey – Microsoft’s internal transformation story
Hear how Microsoft embarked on their own DevOps journey reducing a three-year release cycle down to three weeks. This required changes to their people, process and products. Donovan Brown from the League of Extraordinary Cloud DevOps Advocates will share insights into the agile transformation of Microsoft's Developer Division and showcase newest additions to Azure and how to use Visual Studio Team Services to deploy any language on any platform, including Windows, Linux, mobile and containers.
Meet The Man in the Black Shirt. Donovan Brown is a Principal DevOps Manager on Microsoft's Cloud Developer Advocacy team. Why is DevOps one of the hottest topics? Because it hurts the most. Luckily, Donovan's unofficial tag line is #RubDevOpsOnIt and he's here to make it all better. Before joining Microsoft, Donovan spent seven years as a Process Consultant and a Certified Scrum Master. Developer Tools are his thing. Donovan has traveled the globe helping companies in the U.S., Canada, India, Germany, and the UK develop solutions using agile practices, Visual Studio, and Team Foundation Server in industries as broad as Communications, Health Care, Energy, and Financial Services. What else keeps the wheels spinning on The Man in The Black Shirt? Donovan's also an avid programmer, often finding ways to integrate software into his other hobbies and activities, one of which is Professional Air Hockey where he has ranked as high as 11 in the world.