Future developments in the connected car realm are influenced by two broad trend categories. First, the ever growing and ever evolving demands by consumers. Second, the vast technological changes disrupting the status quo of mobility. The convergence of these overarching trend categories shapes the requirements towards future-ready connected vehicle platforms and their underlying architectural patterns.
Domain-Driven Design (DDD) is an architectural approach that strongly focuses on materializing the business domain in enterprise software through disciplined object-oriented analysis. This session demonstrates first-hand how DDD can be elegantly implemented using Jakarta EE via an open source project named Cargo Tracker.
Cargo Tracker maps DDD concepts like entities, value objects, aggregates and repositories to Jakarta EE code examples in a realistic application. We will also see how DDD concepts like the bounded context are invaluable to designing pragmatic microservices.
The target audience are Software Engineers and Architects that have a basic understanding of Java, containers and the cloud and are keen of sustainability.
I will take a very simple example Java application and demonstrate how it can be refactored to adhere to cloud native principles. Thereby, I will focus on aspects that are relevant for making the application more sustainable: More flexible usage of resources.
This isn’t a talk about microservices, NoSQL, container solutions or hip new frameworks. This talk will show some of the standard Java APIs that are part of Java since version 5, 6, 7 or 8. All those features are very helpful to create maintainable and future-proof applications, regardless of whether JavaEE, Spring, JavaFX or any other framework is used. The talk will give an overview of some important standard concepts and APIs of Java like annotations, null values and concurrency. Based on an overview of this topics and some samples the talk will answer questions like:
The technology landscape is changing at an ever-accelerating speed, and established financial institutions are facing stiff competition from FinTech startups. Rigid architectures, based around risk-avoidance, become a blocker to innovation, where small agile operations can try new things without remorse. Users have gotten accustomed to always-available, instant services, where processing in daily or monthly batches just don't cut it anymore.