September 2017
Intermediate to advanced
50 pages
2h 3m
English
Content preview from Migrating Java to the Cloud
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 3. Modernizing Heritage Applications
Monolithic systems are easier to build and reason about in the initial phases of development. By including every aspect of the entire business domain in a single packaged and deployable unit, teams are able to focus purely on the business domain rather than worrying about distributed systems concerns such as messaging patterns and network failures. Best of breed systems today, from Twitter to Netflix to Amazon, started off as monolithic systems. This gave their teams time to fully understand the business domain and how it all fit together.
Over time, monolithic systems become a tangled, complex mess that no single person can fully understand. A small change to one component may cause a catastrophic error in another due to the use of shared libraries, shared databases, improper packaging, or a host of other reasons. This can make the application difficult to separate into services because the risk of any change is so high.
Our first order of business is to slowly compartmentalize the system by factoring out different components. By defining clear conceptual boundaries within a monolithic system, we can slowly turn those conceptual boundaries—such as package-level boundaries in the same deployable unit—into physical boundaries. We accomplish this by extracting code from the monolith and moving the equivalent functionality into services.
Let’s explore how to define our service boundaries and APIs, while also sharpening the distinction ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.