Businesses are shifting to be powered by technology. This impact means the business architecture is now more influenced by the technical architecture. This presentation discusses what a business architecture would look like that takes advantage of microservices technology. Images are sourced from Google Images

1. Copyright 2018 Porch.com. Confidential. All rights reserved 1

2. Copyright 2018 Porch.com. Confidential. All rights reserved 2

3. Copyright 2018 Porch.com. Confidential. All rights reserved 3
Why chose Microservices?

4. Copyright 2018 Porch.com. Confidential. All rights reserved 4
Why we chose Microservices
Agility – Limited dependencies enable teams to
move quickly with dozens of daily releases
Innovation – Able to build and test quickly, goal
to ship improvements each sprint
Scalability – Design of systems to scale without
scaling headcount; Only 2 Dev Ops
Resilient – services are isolated and failure won’t
bring down the full system

5. Copyright 2018 Porch.com. Confidential. All rights reserved
Distributed microservices architecture enables rapid delivery on top of scalable infrastructure
Micro
Frontend
Services
Micro
Backend
Services
Data
Services
Tech Tool
Chain

6. Copyright 2018 Porch.com. Confidential. All rights reserved 6
Product
Engineering
PRODUCTSQUAD
DEDICATED
Product Manager
Engineering Manager
Software Engineering
SHARED
Data Engineering
Dev Ops
Data Science
UX Designer
Analytics
Marketing & Growth
Each of our product squads
own a set of microservices
as part of the product
architecture and focus on
moving a business metric

7. Copyright 2018 Porch.com. Confidential. All rights reserved 7

8. Copyright 2018 Porch.com. Confidential. All rights reserved 8

9. Copyright 2018 Porch.com. Confidential. All rights reserved 9

10. Copyright 2018 Porch.com. Confidential. All rights reserved 10
Go To
Market
User
Research
Product
Management

11. Copyright 2018 Porch.com. Confidential. All rights reserved
Annual and Quarterly
OKRs to ensure
alignment
A/B test your 2-way
doors
3-6 page narratives
for decision making
11

12. Copyright 2018 Porch.com. Confidential. All rights reserved
Use jobs-to-be-done
to understand the full
journey
Usertesting.com to
quickly test ideas
All product managers
conduct interviews
12

13. Copyright 2018 Porch.com. Confidential. All rights reserved
Agile Methodology –
Prototype and Iterate
Leverage
microservices like a 3-
1 Lego set to create
custom experiences
Instrument & monitor
everything
13

14. Copyright 2018 Porch.com. Confidential. All rights reserved
Smaller and more
frequent messages are
winning
Social is all about
these small moments
Personalized
messages (using large
data to segment and
AI to augment)
14

15. Copyright 2018 Porch.com. Confidential. All rights reserved
Too good to be true… what are the trade offs?
Duplication – teams don’t have to communicate what they are building, can result in
teams building a similar service
Resource allocation –system is not inherently designed to be efficient resource
allocation and thus may see higher usage of cloud services
Multiple Languages – when services of different languages connect require more work
Standardization – hard to enforce standardization and consistency
15

16. Copyright 2018 Porch.com. Confidential. All rights reserved 16
A few closing thoughts
Microservices isn’t just a tech decision,
but a business decision
The benefits of microservices = the
benefits you want in building products
Set design principles before changing
your process

17. Copyright 2018 Porch.com. Confidential. All rights reserved 17