shutterstock-789747985
Containers

How micro should a microservice be?

Microservices are one of the hot new trends in application development. A big part of their appeal is the promise of enabling developers to create applications that are more robust, secure, flexible, and scalable.

But is a microservice-based architecture right for your organization? How much work is involved in switching to microservices? And how micro should a microservice actually be?

 

Monoliths vs Microservices

According to a recent paper by Google on the subject, a monolithic application can be described as “a single deployable unit, e.g. a single WAR file in Java or a single Web Application/Web Site in .NET.”

AWS Chief Architect Glenn Core talks competition and the future. Check out: How Microservices break down legacy monoliths

To continue reading...


PREVIOUS ARTICLE

« Are you at risk from Amazon's S3 bucket problem?

NEXT ARTICLE

Testing the waters: The value of ethical hacking for business »
author_image
Dan Swinhoe

Dan is a journalist at CSO Online. Previously he was Senior Staff Writer at IDG Connect.

  • twt
  • twt
  • twt
  • Mail

Recommended for You

How to (really) evaluate a developer's skillset

Adrian Bridgwater’s deconstruction & analysis of enterprise software

Unicorns are running free in the UK but Brexit poses a tough challenge

Trevor Clawson on the outlook for UK Tech startups

Cloudistics aims to trump Nutanix with 'superconvergence' play

Martin Veitch's inside track on today’s tech trends

Poll

Is your organization fully GDPR compliant?