DevOps.com

Where the world meets DevOps

  • Home
  • Features
  • Neighborhoods
    • Leadership Suite
    • Continuous Delivery
    • Continuous Testing
    • Cloud
    • DevOps Practice
    • DevOps Toolbox
    • DevOps Security
    • Container Journal
    • Microservices Journal
    • ROELBOB
  • Webinars
    • Upcoming
    • On-Demand
  • Library
  • Chat
  • News
  • Directory
  • About
  • Connect
  • News Releases
    • Facebook
    • Google+
    • Linkedin
    • Twitter

Home » Microservices Journal » Spotlight » The Executive’s Guide to Microservices: Chapter 1

The Executive’s Guide to Microservices: Chapter 1

JP MorgenthalBy JP Morgenthal on November 20, 2017 2 Comments

Meet Steve. Steve is responsible for a mission-critical application for a very large enterprise. He has a problem: It takes Steve and his team a very long time to make changes to this application and release it to production. Steve has been talking to vendors, consultants and peers about agile software development techniques and DevOps, but Steve and his team have assessed that his application does not lend itself to these approaches.

 
Recent Posts By JP Morgenthal
  • The Executive’s Guide to Microservices Chapter 3: Choosing A Starting Point
  • The Executive’s Guide to Microservices Chapter 2: The Business Challenge
  • Welcome to Microservices Journal
JP Morgenthal More from JP Morgenthal
Related Posts
  • DevOps Debates: Monoliths or Microservices
  • Docker Names Steve Singh as Chairman and Chief Executive Officer
  • Microservices: Easier Than You Think
    Related Categories
  • Microservices Journal
    Related Topics
  • microservices
  • monolith
  • soa
Show more
Show less
 

See, the system Steve looks after is called a monolith, which is a very confusing title since it was developed using the latest modular software development approaches when it was created, in the latter half of the 1990s and early 2000s. Steve and his team are constantly advised that they need to decompose their monolith into microservices. However, this advice only confuses Steve and his team even more, since the system was designed using a service oriented architecture (SOA) with the intent of ensuring that it was easier to maintain and scale.

 

Steve’s team fell into a very common trap associated with many SOA-based designs: The services were designed with deep dependencies, they share a common database and they are very coarse-grained. Indeed, the collections service, which is one of eight services in the system, handles every potential operation a collections agent might ever need. Modifying any operation within the collections service means the entire collections service must go through regression testing and production must enact a very cumbersome deployment strategy that requires a five-hour maintenance window.

 

Needless to say, Steve cannot keep up with the requested changes from the business with these constraints. Steve’s advisers have given him some good advice on organizing to develop faster, but he would only be applying Band-Aids faster. However, once the constraints identified above had been pointed out to Steve and his team, they better understood the challenge ahead of them.

 

Steve and team are going to have to redefine the data models so they support service independence, then extract subsets of functionality out of the large, intertwined services to deploy as within a well-defined business context—following the “do one thing well” mantra. They then can start to extricate the complex business logic trapped inside the enterprise service bus so it can be incorporated into the services at the edge.

 

Steve and his team realize that continuing to enhance the monolithic code base avoids the challenges of redevelopment but reduces the value of that codebase to the business. While there will be a cost of untangling the monolith, the cost of not doing so is lack of competitiveness, lack of agility, long wait times for new features, possible opportunity loss and continued investment in technical debt. Steve’s job will be to present the justification for this to the business based on these risks.

 

When the task is completed, Steve and team will be able to deploy new services and modify existing services within weeks. The costs related to development and testing will drop significantly and the finer-grained services will allow developers to address business needs more quickly.

 

We’ll check in with Steve and his team as they embark on this journey and deal with the challenges ahead.

  
Sponsored Content
Featured eBook
A New Approach for Securing DevOps Environments in the Cloud

A New Approach for Securing DevOps Environments in the Cloud

Back when IT infrastructures took months to develop and deploy, security and compliance teams had time to configure and release security controls in parallel. But today, high-performing teams deploy on demand or multiple times per day, and they can deploy changes to production in less than an hour.  This rapid ... Read More
 

Filed Under: Microservices Journal, Spotlight Tagged With: microservices, monolith, soa

  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to share on Google+ (Opens in new window)
  • More
  • Click to share on Pinterest (Opens in new window)
  • Click to share on Tumblr (Opens in new window)
« High Availability
DevSecOps: Security Needn’t be Sacrificed for Speed »

Search DevOps.com

Sign up for our newsletter

  • Notice: Submission of this form includes an automatic subscription to the DevOps e-newsletter. DevOps.com Privacy Policy

Upcoming Webinars

Tue 24

Data Privacy – Why your company needs to pay attention to what’s behind the compliance curtain!

Tue, April 24, 11:00 am - 12:00 pm EDT
Tue 24

Measuring DevOps Performance

Tue, April 24, 1:00 pm - 2:00 pm EDT
Wed 25

Frictionless Application Development: Radically Change How You Secure and Monitor Your OpenShift and Kubernetes Environment

Wed, April 25, 1:00 pm - 2:00 pm EDT

More Webinars

Past Webinars

Download Free eBook

Continuous Testing vs. Test Automation
Continuous Testing vs. Test Automation

RSS DevOps Chat

  • DOES London 2018 Preview w/ Mirco Herring, DevOps for the Modern Enterprise April 14, 2018
  • Anything You Can Do With DevOps, You Can Do In A Mainframe, Chris O'Malley, Compuware April 14, 2018
  • Low-Code Is Coming To An App Near You, Appian World Preview April 13, 2018
  • Microservices on Google Cloud Update with Tim Hockin April 12, 2018
  • DevOps Chat: Interop China Features DevOps & DevSecOps April 9, 2018

Past Webinars

DevOps.com Webinar ReplaysDevOps.com Webinar Replays
  • Facebook
  • Google+
  • Linkedin
  • Twitter
  • Home
  • Business Directory
  • About DevOps.com
  • Media Kit
  • Sponsor Info
  • Copyright
  • TOS
  • Privacy Policy

© 2018 · Mediaops, LLC.