Refactoring to a System of Systems - Oliver Gierke

December 14, 2017

Microservices, Serverless Day: Thursday Time: 11:50 Room: 2008 Teams that have built monoliths for years are used to certain patterns of interaction between different parts of the code base. Simply replicating those patterns when splitting up a system into a distributed one usually introduces a lot of complexity and drawbacks that often totally subvert the desired effects of a split up of the system in the first place. The talk takes a look at a concrete sample of monolithic module interactions and identifies the problems that arise if that approach is transferred as-is into a distributed system. We then discuss an alternative variant of the monolithic implementation and how that approach improves the system's modularity for the monolith and how it minimizes the cost and problems when splitting up the monolith or even starting with a system of systems in the first place. Oliver Gierke, Spring Data Project Lead, Pivotal Filmed at SpringOne Platform 2017

Previous
Securing Spring Functions By Breaking In
Securing Spring Functions By Breaking In

Serverless Spring Functions rock the security boat. The fact we dont need to manage servers or capacity rid...

Next Video
Ops in the Time of Serverless Containerized Webscale
Ops in the Time of Serverless Containerized Webscale

Ops in the Time of Serverless Containerized Webscale - Bridget Kromhout, Pivotal Living #opslife makes...