Domenico Musto
Engineering Strategy at Spektrix
London, United Kingdom
Actions
Passionate hands on software architect with over 20 years of experience. Currently working as an Engineering Strategist at Spektrix and previously at AWS focusing on serverless technologies.
I am a strong advocate of distributed systems, ReST, event driven architecture, messaging, automation testing, continuous delivery, agile engineering practices with an obsession for clean code.
Helping the world to get rid of RPC
I am a frequent speaker at international conferences
Area of Expertise
Topics
Development productivity in a post serverless world
The journey from physical computers to functions running in the cloud has changed how engineering teams work forever.
The role of software developers and infrastructure engineers is not what it used to be.
But what is coming next ? What’s beyond devops, containers and serveless ?
In this session we will explore new emerging models for software development which aim to boost productivity and reduce time to market.
Warning: this talk might contain code
Essential Engineering
In today's fast-paced development environment, delivering high-quality software quickly is more critical than ever.
Have you ever wondered how high performing teams create competitive advantages by building better software faster ?
This talk explores the intersection of essential software engineering principles, focusing on architecture patterns and team processes that drive efficiency, scalability and speed.
By the end of the session, attendees will leave with practical techniques they can start using right away to build reliable systems at pace, driving success and meeting critical business objectives.
Safe at any speed with contract testing
You have migrated the monolithic architecture to a distributed system and you live happily in the world of microservices. Your teams want to work independently to add value and increase time to market but the integration between different components and microservices is challenging and complex. How can we make sure that services can change often and independently without breaking the integration with other parts of the system?
In this talk we will explore the concepts of boundary, contract and consumer driven testing and how automation plays a key role in being safe at speed.
From on premise to the cloud with zero downtime
The benefits of the cloud are key to most business but migrating is not easy, it can be disruptive.
What does it take for an application to become "cloud native" ?
What are the key steps for a successful migration of a busy system with little or no disruption,what to consider to make key architecture decisions and how to manage risks using a real life story.
Getting out of the monolith hell
Microservices is the new buzzword in the industry but its meaning seems to be unclear and elusive.
Let's take a step back and look at the original idea behind them. Why are microservices different from SOA ? What are the challenges in splitting a monolithic application into a microservices based architecture ?
In this talk we will go through the key steps for a successful migration with a particular focus on :
- bounded context and business capabilities
- integration patterns
- catalog data
- versioning
- service autonomy
- failure mitigation
- events
Event Driven Architecture in practice
We don't want to have a huge block of code impossible to maintains and extend.
We want to break up the monolithic application into smaller isolated services which are easy to extend and deploy..after all we want to be agile!
Let's see how Event Driven Architecture can help us to have a more scalable application and how services use messaging to communicate.
The objectives of the session:
- overview of an event driven architecture
- advantages
- disadvantages
- integration patterns
Continuous delivery made possible
The Agile Manifesto says “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
That’s nice but..how do we actually do that ? What’s the difference between continuous deployment and continuous integration ?
What does that mean for the business ? How will this change the way we work and write code ? Build an environment which allows us to continuously deliver software in an automated fashion can be very hard, especially in a large fast growing company. In this session we will explore practices, techniques and tools we can use to set up a development process which enables automated deployment.
Architecting and coding for agility: A practical guide
We all know what good code looks like. It’s simple, small, readable and extensible with explicit intent. Above all it is built with SOLID Principles. The question is: is good code enough? If we want systems that are truly agile and that can be changed easily, what other characteristics do the code and architecture of those systems need to have to allow us to re-shape them continuously? In this talk we will look at various design and architectural patterns which allow us to turn good code into truly agile code. All the example will be in .NET Core
How to develop at the speed of light
Ancient tales speak of Jedi developers that knew legendary patterns and techniques which allowed them to develop and test at the speed of light and fear no bugsThey said that your hexagonal architecture can benefit from using the Command Processor pattern and its components would be extremely decoupled with well defined boundaries and integration contracts.Extremists thought that these techniques would easily enable the use of CQRS and Event Sourcing and that your data would never be inconsistent again.Others could even turn a complex application into an event driven distributed system hosted by serverless infrastructure.Let's see how!
Getting out of the monolithic hell
Microservices is the new buzzword in the industry but its meaning seems to be unclear and elusive.Let's take a step back and look at the original idea behind them. Why are microservices different from SOA ? What are the challenges in splitting a monolithic application into a microservices based architecture ?In this talk we will go through a real architecture migration story and you will learn the key steps for breaking up your monolith :
-identifying business capabilities
- communication patterns
- catalog data - service autonomy
- service discovery
- failure mitigation
We will also talk about the impact and the benefits that this kind of architecture has on your company as a whole and how would that change the way you think and evolve your product.
Architecting and coding for agility: A practical guide
We all know what good code looks like. It’s simple, small, readable and extensible with explicit intent. Above all it is built with SOLID Principles.
The question is: is good code enough? If we want systems that are truly agile and that can be changed easily, what other characteristics do the code and architecture of those systems need to have to allow us to re-shape them continuously?
In this talk we will look at various design and architectural patterns which allow us to turn good code into truly agile code. All the example will be in .NET Core
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