In the era of LLM and GPT, how can you make models that is fine tuned to your own dataset? This session will also cover tips on how to make it effective.
In the era of LLM and GPT, how can you make models that is fine tuned to your own dataset? This session will also cover tips on how to make it effective.
Microservices are ubiquitous. However, most companies that implement microservices do not reap their full benefits – at best. At worst, it’s an epic failure.
There are reasons for microservices: independent deployment of business capabilities. However, the unspoken assumption is that you need to deploy all capabilities all the time. My experience has shown me that it’s plain wrong. Some capabilities need frequent deployment, while some are much more stable. In “the past”, we used Rule Engines to allow updating business rules without deployment. While it solved the problem, this approach had issues. Between introducing a Rule Engine and migrating your complete system to microservices, I believe that there’s a middle path, and that this path is Function-as-a-Service.
In this talk, I’ll detail every point I’ve made above, and show how one can use Serverless to pragmatically design a system that allows deploying as often as you need.
Command Query Responsibility Segregation (CQRS) is a proven design pattern that enables the clear separation of data changes (commands) and data queries (queries). This separation allows these responsibilities to be scaled and optimized independently. The application code is also structured more understandably, which improves maintainability.
In this talk, the understanding of the practical implementation of the CQRS principles will be deepened and implemented using modern Java language features such as records, switch expressions, and pattern matching.
An example application is used to demonstrate how the theoretical foundations of CQRS can be applied in practice and how this affects application design while increasing data access efficiency.
This session is a review of commonly recurring bad UX with clear examples of showing the better way of doing it. Examples will include global and local sites/apps.
* Limited hybrid tickets available.
First-come, first served!