BoundedContexts

I was just reading this:
https://www.nginx.com/microservices-soa/?utm_source=nginx&utm_medium=homepage&utm_campaign=microservices_soa

And noticed some new "terminology".

""Realistically, there will always be some services that are shared,
even in a microservices architecture (for example, infrastructure
serv‐ ices). However, whereas SOA tries to maximize component sharing,
microservices architecture tries to minimize on sharing, through the
concept of a bounded context. One way to achieve a bounded con‐ text
and minimize dependencies in extreme cases is to violate the Don’t
Repeat Yourself (DRY) principle and replicate common func‐ tionality
across services to achieve total independence. Another way is to
compile relatively static modules into shared libraries that ser‐ vice
components can use in either a compile-time or runtime bind‐ ing. My
friend and colleague Neal Ford takes a slightly different view of this
by saying that microservices architecture is a share-nothing
architecture with the exception of two things—how services inte‐ grate
with one another, and the infrastructure plumbing to ensure
engineering consistency."

Has anyone seen the term used in this way before?

Greg

-- 
Studying for the Turing test


------------------------------------
Posted by: Greg Young <[email protected]>
------------------------------------


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/domaindrivendesign/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/domaindrivendesign/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/