patterns1.pdf - Escaping monolithic hell This chapter covers The symptoms of monolithic hell and how to escape it by adopting the microservice

patterns1.pdf - Escaping monolithic hell This chapter...

This preview shows page 1 - 3 out of 20 pages.

1Escaping monolithic hellIt was only Monday lunchtime, but Mary, the CTO of Food to Go, Inc. (FTGO), wasalready feeling frustrated. Her day had started off really well. She had spent theprevious week with other software architects and developers at an excellent confer-ence learning about the latest software development techniques, including contin-uous deployment and the microservice architecture. Mary had also met up with herformer computer science classmates from North Carolina A&T State and sharedtechnology leadership war stories. The conference had left her feeling empoweredand eager to improve how FTGO develops software.This chapter coversThe symptoms of monolithic hell and how to escape it by adopting the microservice architectureThe essential characteristics of the microservice architecture and its benefits and drawbacksHow microservices enable the DevOps style of development of large, complex applicationsThe microservice architecture pattern language and why you should use it
2CHAPTER1Escaping monolithic hellUnfortunately, that feeling had quickly evaporated. She had just spent the firstmorning back in the office in yet another painful meeting with senior engineeringand business people. They had spent two hours discussing why the development teamwas going to miss another critical release date. Sadly, this kind of meeting had becomeincreasingly common over the past few years. Despite adopting agile, the pace of devel-opment was slowing down, making it next to impossible to meet the business’s goals.And, to make matters worse, there didn’t seem to be a simple solution.The conference had made Mary realize that FTGO was suffering from a case ofmonolithic helland that the cure was to adopt the microservice architecture. But themicroservice architecture and the associated state-of-the-art software developmentpractices described at the conference felt like an elusive dream. It was unclear to Maryhow she could fight today’s fires while simultaneously improving the way software wasdeveloped at FTGO.Fortunately, as you will learn in this book, there is a way. But first, let’s look at theproblems that FTGO is facing and how they got there.1.1The slow march toward monolithic hellSince its launch in late 2005, FTGO had grown by leaps and bounds. Today, it’s one ofthe leading online food delivery companies in the United States. The business evenplans to expand overseas, although those plans are in jeopardy because of delays inimplementing the necessary features.At its core, the FTGO application is quite simple. Consumers use the FTGO web-site or mobile application to place food orders at local restaurants. FTGO coordinatesa network of couriers who deliver the orders. It’s also responsible for paying couriersand restaurants. Restaurants use the FTGO website to edit their menus and manageorders. The application uses various web services, including Stripe for payments,Twilio for messaging, and Amazon Simple Email Service (SES) for email.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture