WILL

SOA

HELP?

DOWNSIDE

• How do we deploy?
• API overhead
• SOA Anti-patterns
• Learning curve
• Tooling

UPSIDE

• Deploy isolated work
• Scale what you need
• Logic compartmentalization
• Break things in isolation
• When its time to rewrite, it's less painful
• Stand-alone development
• Authentication
• Unblock shipping

Choices

• Monolith first?
• Tech debt?
• Velocity and economies of scale?
• What goes into this service?
• How many stacks?
• How many layers?

Monolith first

WHAT

IT LOOKS LIKE

PITFALLS

Write an SDK

Text

HOW TO GET

THERE

"For some SOA implies an architecture where applications disappear."

snippet from "ServiceOrientedAmbiguity" on Martin Fowler's blog

RESOURCES

http://simplicable.com/new/10-soa-design-patterns-every-architect-should-know

http://www.ibm.com/developerworks/library/wa-soa_antipattern/index.html

http://martinfowler.com/bliki/ServiceOrientedAmbiguity.html

Q
    &
        A