The Pros and Cons of Microservices
August 25, 2020

Rod Cope
Perforce

Microservices have changed software development and promise powerful benefits. Instead of traditional monolithic architectures, individual teams create small pieces of functionality, which are then added up to be the whole. These smaller pieces are easier to replace, and years have not been dedicated to creating a particular microservice and being locked into one platform.

Also, it is theoretically easier to be innovative and responsive, and to scale up to meet additional user load or demand, compared to a monolithic app, where the entire architecture essentially has to be cloned (another copy of the database, the web server and the app server).

Microservices fit in well with open source, largely because microservices depend on container orchestration tools, which happen to be open source, and many related tools — such as service meshes — are predominantly open source packages.

The Pros and Cons

For some organizations, microservices enable the agility that modern software development needs. However, it is a big step: some organizations have already struggled with Agile and DevOps adoption: microservices are an even bigger challenge. Gartner has previously predicted that the majority of organizations will find microservices too disruptive and will look at alternatives.

To give this some context, here is an example. Imagine an ecommerce app for online checkout, involving pricing, a shipping calculator, and an inventory all working together. Then imagine it is Thanksgiving, and the website is being overwhelmed by enquiries from a particular zip code. With microservices, it is relatively simple to spin up a new instance to handle the extra load, compared to a monolith, which would require another instance of the entire app.

However, the amount of effort to coordinate all of the moving parts can increase dramatically. To work in harmony, microservices need continual monitoring and a view of the bigger picture. While they are loosely coupled, in fact microservices may depend on a couple of others to perform well. So, if a version changes, there must be a way to notify related microservices teams, but without creating a lock-step situation. Service meshes can help make systems more resilient, but even so, microservices can easily lead to uncontrollable chaos if not planned appropriately.

Alternatives to Microservices

An alternative approach is macroservices, using chunks of previously-proven parts of the monolith, but bring legacy problems. These include code that is hard to read, or it may be difficult to get a workable public API, and testing and scaling-up may be challenging.

Another option is to use miniservices, where two or three share the same database, unlike microservices which each have their own data storage. Miniservices are independent but coordinated. There is the downside risk of "miniservices creep," caused by teams adding more shared data stores, APIs, and other features. This can lead to a bloated environment, so miniservices need a lot of control from team leaders.

Playing devil's advocate, is a wholesale move away from monoliths always necessary? If new releases are rare, a monolith may be fine for the moment. Agile and DevOps, with some help from REST APIs, can improve efficiency. However, it is likely that for any organization, at some point, a more flexible way of working will become imperative.

Team Culture is Everything

The bottom line is that there is no one-size-fits-all approach to modern software architectures; each have their pros and cons. Furthermore, the importance of the cultural approach outweighs the choice of architecture. Failure might be blamed on microservices, whereas it could have worked with the right team culture. Sure, tools like API management, version control, and automated testing help, but they are not the answer on their own.

An incremental move away from monoliths is another option, perhaps just transitioning the parts of an app that change most often, which will also give the organization some experience of what does — or doesn't — work, before making a bigger commitment to another approach.

New ways of developing software have huge potential for flexibility, innovation, and time-to-market, but regardless of which structure is chosen, the impact on the culture cannot be under-estimated.

Rod Cope is CTO of Perforce
Share this

Industry News

May 12, 2025

LambdaTest, a unified agentic AI and cloud engineering platform, has announced its partnership with MacStadium(link is external), the industry-leading private Mac cloud provider enabling enterprise macOS workloads, to accelerate its AI-native software testing by leveraging Apple Silicon.

May 12, 2025

Tricentis announced a new capability that injects Tricentis’ AI-driven testing intelligence into SAP’s integrated toolchain, part of RISE with SAP methodology.

May 12, 2025

Zencoder announced the launch of Zen Agents, delivering two innovations that transform AI-assisted development: a platform enabling teams to create and share custom agents organization-wide, and an open-source marketplace for community-contributed agents.

May 08, 2025

AWS announced the preview of the Amazon Q Developer integration in GitHub.

May 08, 2025

The OpenSearch Software Foundation, the vendor-neutral home for the OpenSearch Project, announced the general availability of OpenSearch 3.0.

May 08, 2025

Jozu raised $4 million in seed funding.

May 07, 2025

Wix.com announced the launch of the Wix Model Context Protocol (MCP) Server.

May 07, 2025

Pulumi announced Pulumi IDP, a new internal developer platform that accelerates cloud infrastructure delivery for organizations at any scale.

May 07, 2025

Qt Group announced plans for significant expansion of the Qt platform and ecosystem.

May 07, 2025

Testsigma introduced autonomous testing capabilities to its automation suite — powered by AI coworkers that collaborate with QA teams to simplify testing, speed up releases, and elevate software quality.

May 06, 2025

Google is rolling out an updated Gemini 2.5 Pro model with significantly enhanced coding capabilities.

May 06, 2025

BrowserStack announced the acquisition of Requestly, the open-source HTTP interception and API mocking tool that eliminates critical bottlenecks in modern web development.

May 06, 2025

Jitterbit announced the evolution of its unified AI-infused low-code Harmony platform to deliver accountable, layered AI technology — including enterprise-ready AI agents — across its entire product portfolio.

May 05, 2025

The Cloud Native Computing Foundation® (CNCF®), which builds sustainable ecosystems for cloud native software, and Synadia announced that the NATS project will continue to thrive in the cloud native open source ecosystem of the CNCF with Synadia’s continued support and involvement.

May 05, 2025

RapDev announced the launch of Arlo, an AI Agent for ServiceNow designed to transform how enterprises manage operational workflows, risk, and service delivery.