Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Cloud Foundry for Developers

You're reading from   Cloud Foundry for Developers Deploy, manage, and orchestrate cloud-native applications with ease

Arrow left icon
Product type Paperback
Published in Nov 2017
Publisher Packt
ISBN-13 9781788391443
Length 306 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (3):
Arrow left icon
David Wu David Wu
Author Profile Icon David Wu
David Wu
Rick Farmer Rick Farmer
Author Profile Icon Rick Farmer
Rick Farmer
Rahul Kumar Jain Rahul Kumar Jain
Author Profile Icon Rahul Kumar Jain
Rahul Kumar Jain
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Cloud Foundry Introduction FREE CHAPTER 2. Cloud Foundry CLI and Apps Manager 3. Getting Started with PCF Dev 4. Users, Orgs, Spaces, and Roles 5. Architecting and Building Apps for the Cloud 6. Deploying Apps to Cloud Foundry 7. Microservices and Worker Applications 8. Services and Service Brokers 9. Buildpacks 10. Troubleshooting Applications in Cloud Foundry 11. Continuous Integration and Continuous Deployment

Modernizing the monolith


The approach of modernizing an application towards cloud-native maturity leads to an application that is highly scalable and resilient. We discussed how a cloud-native application could scale a component of an application rather than scaling the entire application. Consider the scenario where a search component, that represents 50 Megabytes of memory used, of a monolithic application that requires 1 Gigabyte of memory. The monolithic application then experiences double the load on the search component. Naturally, we would scale the instance by two, which would result in 2 Gigabytes of memory used in total. If we were to extract out the search component as a Microservice, we would be able to able to scale only the search component.

In an ideal world, ignoring potential memory setup overheads of a separate microservice application, it would mean that we would have had only increased the total application memory usage to 1.1 Gigabytes. That's a significant 45% saving...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image