How can a small team handle infrastructure complexities that come with Microservices and still deliver business and user value?
The short answer to that could be to build your core domain - that differentiates you from your competitors - in-house and outsource undifferentiating commodities to utility suppliers.
In this talk I have used Wardley Maps to visualise how the value chain can evolve when getting infrastructure components handled by different options: Going from open source software to Kubernetes' container orchestration, to Istio's service mesh and to Serverless technologies, such as AWS Lambda.
35. Wardley Maps
ValueChain
InvisibleVisible
Genesis Custom-Built Product (+rental) Commodity (+utility)
Evolution
Uncharted Industrialised
Chaotic
Uncertain
Unpredictable
Changing
...
Ordered
Known
Measured
Stable
...
By Simon Wardley
Position
Movement
Visualisation of a value chain’s evolution
@suksr
36. Who are your users?
ValueChain
InvisibleVisible
Wardley Maps
Value Chain
@suksr
37. Who are your users?
What are your users’ needs?
ValueChain
InvisibleVisible
Wardley Maps
Value Chain
@suksr
38. Who are your users?
What are your users’ needs?
What are the components/activities to fulfil
your users’ needs incl. dependencies?
ValueChain
InvisibleVisible
Wardley Maps
Value Chain
Position
@suksr
83. Serverless
AWS Building Blocks
Lambda
API Gateway
SNS
SQS
DynamoDB
Step Functions
Core AWS Serverless Building Blocks
S3
Kinesis
CloudWatch
Cognito
@suksr
IAM
and more