Home > Articles

Designing the Application

Microsoft Azure team members Boris Scholl, Daniel Fernandez, and Trent Swanson cover some considerations for architecting and designing an application using a microservice architectural style, as well as the paths to a microservices architecture.

This chapter is from the book

In this chapter we will cover some considerations for architecting and designing an application using a microservice architectural style, as well as the paths to a microservices architecture. How do we go about defining the boundaries for the various services and how big should each service be? Before we dive into defining boundaries, let’s pause to consider whether or not this is the best approach for the project currently. Sometimes the path to a microservices architecture actually starts with something closer to a monolith.

Most of the successful microservices examples we have to draw experiences from today actually started out as monoliths that evolved into a microservices architecture. That doesn’t necessarily mean we can’t start a project with a microservices architectural approach, but it’s something we will need to carefully consider. If the team doesn’t have a lot of experience with this approach, that can cause additional risk. Microservices architecture has a cost that the project might not be ready to assume at the start. We will cover more of these considerations in detail along with some thoughts on defining service boundaries.

Determining Where to Start

Before we jump into designing our microservices and breaking down the business domain, let’s first pause to think about whether or not we should start with microservice architecture or plan to eventually work our way to it. There’s absolutely nothing wrong with a monolithic architecture for the right project today, and sometimes it’s a good place to start. It might even be the case that we can start somewhere in between. A microservices architecture has an up-front cost that can slow the initial release and make it more difficult to get to a minimum viable product quickly, especially in a startup situation. The other thing to consider is the current and future size of the team and the application. If the application is not going to scale to a size that it makes it worthwhile, then we might want to reconsider a microservices approach. Do we have the skills and necessary DevOps practices in place to make it successful? What skills and practices are needed and when can we get them? These are all things we need to consider.

Coarse-Grained Services

A microservices architecture introduces a lot of moving parts, and the initial costs will be higher. It’s often better to start with a few coarse-grained, self-contained services, and then decompose them into more fine-grained services as the application matures. With a new project, starting with a monolith or more coarse-grained services can enable us to initially bring a product to market more quickly today. Architects, developers, and operations are often more familiar with the approach, and the tools we use today have been created to work well with this method. As we bring the new application to market, we can further develop the skills necessary to managing a microservices architecture. The application boundaries will be much more stable and we can better understand where our boundaries should be.

If we do decide to start with something on the monolithic end of the spectrum, there are some considerations to take into account for approaching the design if we plan to transition to a microservices architecture. We could carefully design the application, while paying close attention to the modularity of the application to simplify the migration to microservices. This is great in theory, but in practice, maintaining modularity in a monolith can be challenging. It requires a lot of discipline to build a monolith in a way that it can easily be refactored into a microservices architecture.

In some situations, there is absolutely nothing wrong with planning to build a monolith that gets us to market quickly, then replacing it with a microservices architecture and simply discarding the monolith. This requires some planning for how the monolith will eventually be displaced when the time comes.

Depending on the business and technical requirements, as well as the experience and knowledge of the team, we can start at or somewhere between a monolith and fine-grained microservices, as we see in Figure 3.1. Applications with requirements that have more to gain from microservices can start closer to the right on this graph, and teams with less experience can start closer to the left, with plans to further decompose as needed.

Figure 3.1

Figure 3.1: Evolution of a monolith to a microservices architecture

A valid approach would be to start with fewer coarse-grained services and split them into more fine-grained services over time. We would still break the application up using the same principles and practices for service decomposition and design as we would when approaching a microservices architecture. We can then determine how ready we are with the operational aspects for microservices, and as the team’s experience, tools, and processes mature, we can move to finer-grained services. If we are struggling with only a few services, then managing a dozen is going to be painful.

Starting with Microservices

As we mentioned earlier, there is no reason we cannot start with a monolith or more course-grained services. It could be that we have a very large team that is working on a new large-scale application, and the domain is well-understood. The counter-argument to starting with a monolith is that if we know our end goal is a microservices architecture, then there might be good reason to start there from the beginning.

By starting with a microservices architecture, we can avoid the cost of refactoring later on, and potentially reap the benefits of microservices earlier. We ensure our carefully designed components and boundaries don’t become tightly coupled, and based on history they generally will to some degree in a single codebase. The team becomes very familiar with building and managing a microservices-based application from the start. They are able to develop the necessary experience, and build out the necessary infrastructure and tooling to support a microservices architecture. There is no need to worry about whether or not we re-architect it someday, and we avoid some potential technical debt. As the tools and technologies mature, it can be easier to start with this approach.

Once we have made this decision, we will either have a monolith we need to refactor, or a new application we need to build using some combination of coarse- and fine-grained services. Either way, we need to think about approaches to breaking down an application into the parts suitable for a microservices architecture.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020