Thomas Presthus
Consultant and general ninja
Tønsberg, Norway
Actions
Thomas is a consultant from Norway who specializes in software architecture and development. He’s been a practitioner of Domain-Driven Design for the past 10 years or so, and finds great joy in pondering in business problems. Clients and colleagues knows him as an energetic and passionate craftsman who loves to learn, experiment, fail and succeed while sharing his own experiences and knowledge.
Having worked with too many languages and technologies to mention, Thomas has found the intersection between business and IT to be a far more rewarding approach to problem solving and easing up the everyday work of software development. He’s known for holding workshops and talks for both his clients and at local user groups.
Area of Expertise
Topics
Evolving compositional user interfaces
Ever since we started breaking applications into services, be it in the era of SOA or more recently with microservices, we’ve struggled to incorporate user interfaces into our decoupled, distributed architectures. We’ve seen frontends versioned separately with tight coupling to our services, breaking cohesion. We’ve seen the rise of Backend-For-Frontend and the emerge of micro frontends. We talk about composition, yet so many projects fail to implement actual composition. Instead we end up with some kind of compromise, with repeated business logic in the front-end, back-end and API, making it hard to scale – especially when multiple teams are involved – causing lock-step deployment, latency, bottlenecks and coordination issues.
What if we could find a viable solution that allowed us to scale development, keep distribution and cohesion and also provide composition of user interfaces?
In this talk you are introduced to the evolution of compositional user interfaces and existing patterns while we discover their pros and cons, before diving into the architecture and development of compositional interfaces using hypermedia and micro-frontends. We go beyond the simple “Hello World” example that always seems to work, and you’ll learn patterns in modelling and design that will get you up and running with decoupled, composed user interfaces in your day job.
NDC Oslo 2019 Sessionize Event
µCon London 2019 - The Conference on Microservices, DDD & Software Architecture
Ever since developers started breaking applications into services, be it in the era of SOA or more recently with microservices, they’ve struggled to incorporate user interfaces into their decoupled, distributed architectures.
We’ve all seen frontends versioned separately with tight coupling to dependent services, breaking cohesion. The rise of Backend-For-Frontend is real and so is the emerge of micro frontends. We all talk about composition, yet so many projects fail to implement actual composition. The result seem to be some kind of compromise proving hard to scale when multiple teams are involved - causing lock-step deployment, latency, bottlenecks and coordination issues.
What if you could find a viable solution that allowed you to scale development, keep distribution and cohesion and also provide composition of user interfaces?
This talk explores the different patterns available, and attempts to pinpoint their pros and cons, effectively serving as guidance to implementing proper composition. Thomas will go beyond the simple “Hello World” example that always seems to work, and you’ll learn patterns in modelling and designing that can actually be employed for composition.
DDD eXchange 2018
https://skillsmatter.com/skillscasts/11499-cleaning-up-an-unwieldy-monolith-without-using-microservices
As a practitioner of domain-driven design, Thomas wants to model and align his software with the business, but, like many of you, has experienced how legacy code bases holds him back. They provide value, but are often constraining, making it harder to apply domain-driven design. Have you not fantasized about the greenfield rewrite with proper models and abstractions, only to realize how hopeless it would be? Enter microservices: The promised land and seemingly silver bullet for tidying up an unwieldy monolith. They certainly appear tempting, but aren’t suitable for all of us, and cleaning up a messy monolith really isn’t their job. Eric Evans proposed the notion of bubble contexts back in 2012 as a means to create space for modelling in a legacy system. Perhaps we could take a step back and build a better understanding of our monoliths’ boundaries using this heritage.
This case study will look into how we started our journey of cleaning up a mission-critical monolith at a major Scandinavian payment solutions provider using bubble contexts and other aspects from domain-driven design. Using these we found a low-risk method of attacking our monolith and how to structure it based on our newfound insights of the domain.
You will learn how we took control over our monolith using DDD, why we chose not to use microservices - as well as both the failures and successes we had. You will also learn more technical details of some of the techniques we employed, and how we went about to adjust our surrounding organization to start thinking about business and development as one.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top