© 2015 software ag. all rights reserved. lessons learned from soa-fying a monolith

© 2015 Software AG. All rights reserved.

Lessons Learnedfrom SOA-fying a Monolith

Onceupona time…

Stefan Macke

http://soa.rocks

anwendungsentwicklerpodcast.de

@StefanMacke

ArchitecturalTechnical Organizational

Spanish

English

German

ARGH

Requirements

© Highlander Productions Ltd.

Technical Lessons Learned

Don‘t underestimate the

infrastructure.

Automateeverything.

Test everything.

Slow and steady wins the race.

Nothing is

impossible.

Architectural Lessons Learned

Don‘t put

logic in the ESB!

The ESB is a single point of

failure.

Think about

error handling right from the start.

Do the same for

transactions.

Changing interfaces

hurts.

SOAP is

dead.

There is nocanonical data model.

© Lucasfilm Ltd.

Understand

loose coupling.

Avoid

redundancy.

Organizational Lessons Learned

SOA requires a new way of

thinking.

Make use of

diversity.

There‘s something in it

for everyone.

You need

an architect.

PersonalLessons Learned

Don‘t blindly trust

consultants.

Question your

beliefs.

Learn from your

mistakes.

Talk about your journey.

to be continued…

© 2015 Software AG. All rights reserved.

Lessons Learnedfrom SOA-fying a Monolith