tagged by:microservices


API bet188足球design·academia·agile·agile adoption·analysis patterns·application architecture·application integration·bad things·big data·board games·build scripting·certification·clean code·collaboration·computer history·conference panels·conferences·continuous delivery·database·bet188足球·dictionary·distributed computing magazine·diversions·diversity·documentation·domain driven bet188足球design·domain specific language·domestic·encapsulation·enterprise architecture·estimation·event architectures·evolutionary bet188足球design·expositional architectures·extreme programming·gadgets·ieeeSoftware·infodecks·internet culture·interviews·language feature·language workbench·lean·legacy rehab·legal·metrics·microservices·microsoft·mobile·model-view-controller·noSQL·object collaboration bet188足球design·parser generators·photography·podcast·popular·presentations·privacy·process theory·productivity·programming platforms·project planning·projects·recruiting·188足球比分直播·188足球比分直播refactoring boundary·requirements analysis·retrospective·ruby·scrum·security·software craftsmanship·talk videos·team environment·team organization·technical debt·technical leadership·test categories·testing·thoughtworks·tools·travel·uml·version control·web development·web services·website·writing


All Content

118金宝博 网页

by James Lewis and 188bet足球充值Martin Fowler

The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of bet188足球designing software applications as suites of independently deployable services.While there is no precise definition of this architectural style,there are certain common characteristics around organization around business capability,automated deployment,intelligence in the endpoints,and decentralized control of languages and data.

25 March 2014


How to break a Monolith into Microservices

by Zhamak Dehghani

As monolithic systems become too large to deal with,many enterprises are drawn to breaking them down into the microservices architectural style.It is a worthwhile journey,but not an easy one.We've learned that to do this well,we need to start with a simple service,but then draw out services that are based on vertical capabilities that are important to the business and subject to frequent change.These services should be large at first and preferably not dependent upon the remaining monolith.We should ensure that each step of migration represents an atomic improvement to the overall architecture.

24 April 2018


Microservice Trade-Offs

Many development teams have found the microservices architectural style to be a superior approach to a monolithic architecture.But other teams have found them to be a productivity-sapping burden.Like any architectural style,microservices bring costs and benefits.To make a sensible choice you have to understand these and apply them to your specific context.

1 July 2015


Microservices and the First Law of Distributed Objects

In P of EAA I said "don't distribute your objects".Does this advice contradict my interest in Microservices?

13 August 2014



Infrastructure as code is the approach to defining computing and network infrastructure through source code that can then be treated just like any software system.Such code can be kept in source control to allow auditability andReproducibleBuilds,subject to testing practices,and the full discipline ofContinuousDelivery.It's an approach that's been used over the last decade to deal with growingCloudComputingplatforms and will become the dominant way to handle computing infrastructure in the next.

1 March 2016



As I talk to people about using amicroservices architectural styleI hear a lot of optimism.Developers enjoy working with smaller units and have expectations of better modularity than with monoliths.But as with any architectural decision there are trade-offs.In particular with microservices there are serious consequences for operations,who now have to handle an ecosystem of small services rather than a single,well-defined monolith.Consequently if you don't have certain baseline competencies,you shouldn't consider using the microservice style.

28 August 2014


Microservices Talk

As with any bit of new architectural terminology,it's hard to get a decent definition of what microservices are,so this talk kicks off by tackling that,based on the article by James and I that helped fuel the interest.I then compare microservices to SOA,compare the architecture to a more monolithic approach,and outline important things you have to get right before you should deploy a microservice application.

15 January 2015


How to extract a data-rich service from a monolith

by Praful Todkar

When breaking monoliths into smaller services,the hardest part is actually breaking up the data that lives in the database of the monolith.To extract a data-rich service,it is useful to follow a series of steps which retain a single write-copy of the data at all times.The steps begin by making a logical separation in the existing monolith: splitting service behavior into a separate module,then separating data into a separate table.These elements can be separately moved into a new autonomous service.

30 August 2018


Testing Strategies in a Microservice Architecture

by Toby Clemson

There has been a shift in service based architectures over the last few years towards smaller,more focussed "micro" services.There are many benefits with this approach such as the ability to independently deploy,scale and maintain each component and parallelize development across multiple teams.However,once these additional network partitions have been introduced,the testing strategies that applied for monolithic in process applications need to be reconsidered.Here,we plan to discuss a number of approaches for managing the additional testing complexity of multiple independently deployable components as well as how to have tests and the application remain correct despite having multiple teams each acting as guardians for different services.

18 November 2014


Don't start with a monolith

by Stefan Tilkov

In the last few months,I've heard repeatedly that the only way toget to a successful microservices architecture is by starting with amonolith first.Toparaphrase Simon Brown: If you can't build a well-structuredmonolith,what makes you think you can build a well-structured set ofmicroservices?The most recent – and,as usual,very convincing –rendering of this argument comes from 188bet足球充值Martin Fowler on this very site.As I hada chance to comment on an earlier draft,I had some time to thinkabout this.And I did,especially because I usually find myself inagreement with him,and some others whose views I typically shareseemed to agree with him,too.

I'm firmly convinced that starting with a monolith is usually exactly thewrong thing to do.

9 June 2015



Themicroservices architectural stylehas been the hot topic over the last year.At the recentO'Reilly software architecture conference,it seemed like every session talked about microservices.Enough to get everyone's over-hyped-bullshit detector up and flashing.One of the consequences of this is that we've seen teams be too eager to embrace microservices,not realizing that microservices introduce complexity on their own account.This adds a premium to a project's cost and risk - one that often gets projects into serious trouble.

13 May 2015



As I hear stories about teams using amicroservices architecture,I've noticed a common pattern.

  1. Almost all the successful microservice stories have started with a monolith that got too big and was broken up
  2. Almost all the cases where I've heard of a system that was built as a microservice system from scratch,it has ended up in serious trouble.

This pattern has led many of my colleagues to argue thatyou shouldn't start a new project with microservices,even if you're sure your application will be big enough to make it worthwhile..

3 June 2015