Daniel Pötzinger
Flamingo
Inspiring Commerce Frontend made in Go
Application Development

20 years experience of building and scaling enterprise web
applications

Blazing fast commerce experience layer
Open sources with from

We open sourced Flamingo!
Why? And what is it?

Soooo.. you really created
your own e-commerce
framework ?
Not really - its more the
”commerce” frontend application
supposed to connect to your
service architecture

Ok but still there should be
a lot solutions out there
Yes… and No…
.. in fact we also used a lot of active
and reliable open source libs.
But hear our complete story..

Motivation
Trends in e-commerce

More Personalization
More targeted Content
Marketplaces &
Collaborations

Scaling with Microservices Headless Commerce
FE 1 FE 2
API 1 API 2
Partner
e commerce architecture

Motivation
Observations in the last years

Big
e-commerce /
shop system

PIM OrderMgmt
Stockhandling Payment
Campaign “Enterprise”
Search Recommendation
Customer data …
Soomuch in itthat I don’t need
I have thatalready

Unflexibleand fixed
High developer ramp up time

HIGHTRAFFIC
Need heavy caching

After rolling out many of
these monolithic systems…

Frustrated
development
teams
Spend lot of $$ in
• Caching and
performance
• Building export
and imports to
other systems

..can we do better?
Fundamental decisions

How would you love to develop
commerce applications?
Is PHP still the right development
language for this?
??

How would you love to develop commerce applications?
• Performance:
Highly dynamic fast content rendering Individual Personalization and Context aware
rendering
• Clean architecture
• Flexibility in a Microservice architecture:
Flexible to use in microservice oriented individual architectures. Useable with
„headless“ (commerce) services No Build and deploy overhead
• Frontend development flexibility:
Decouple frontend build pipeline from „backend“ logic
• Testability
• Developer Experience:
Effective and Fun to use * low learning curve
• Open Source

Is PHP the right development language for this?
• Webserver included
• Compiled / Type Safe
• Concurrency
• Easy to learn - build to scale
• Supported by Google
• Increasing Interest and Success

Lets build something new - with the experience we collected
And go Open Source with it
2016 / 2017

Ecosystem
Carotene
Flamingo is an open
source framework
written in Go.
Use Flamingo Core to
build sophisticated web
applications with
tailored frontends.
Flamingo Commerce:
Your head for
headless
e-commerce
Npm modules that
provide frontend build
pipeline – featuring
pug, sass, webpack
and atomic design
pattern

Frontend
Backend for Frontend
web application architecture
Other Services Other Services
• Anti corruption layer
for the (tightly)
coupled frontend
• Serverside logic
• Data security and IT
security
• Experience / view
layer
• Can be MPA, SPA,
PWA
connect / resilience

Frontend
Backend for Frontend
Core and Framework Modules
Commerce Domains
Product Cart …
ComponentsTemplates Pages+ =
Carotene

Multi Page Application Single Page Application Progressive Web App
• Serverside rendered
• Still king for fast rendering
times.
• Still king for best SEO.
• Usage of progressive
enhancement
• High user interaction
• Usage of SPA frameworks
(React/Vue)
Enhance with offline features
through service workers
frontend architecture
Despite the PWA hype - you will still need serverside
rendering and MPA

Clean architecture
Domain Driven Design Ports and Adapters

Flamingo commerce
Bounded Contexts with its domain models
Cart
• Mutli delivery
• Multi payment
Product
• Product Types
• Simple
• Configurable
Search
• SearchService
• Documents
…

CartProduct Search
…
• Easy to use and decoupled
• Potent models
• Technology neutral domain model
Flamingo commerce
Bounded Contexts with its domain models

Flamingo – Ports and Adapters
Technology Free Domain Model
Application Use Cases
Adapters to the outside / Web Controllers
Technical details (e.g. accessing a microservice)

Domain of “Product”
Context
Application Layer
Flamingo – Ports and Adapters
<<interface>>
ProductService
.Get (id)
Used as primary port:
• The product service is called from the
interface layer for example
(in a ProductViewController)
ProductController
.ViewAction
Product

Domain of “Product”
Context
Application Layer
Flamingo – Ports and Adapters
<<interface>>
ProductService
.Get (id)
ProductController
.ViewAction
Infrastructure Layer
ProductServiceAdapter
Get (id) {…}
Used as secondary port:
• The product service is implemented
by a secondary adapter
Product

Flamingo commerce – Bounded Contexts
CartProduct Search
…
Magento Adapter Module

Flamingo commerce – Bounded Contexts
CartProduct Search
…
Commercetools Adapter Module

Flamingo commerce – Bounded Contexts
CartProduct Search
…
Standalone Adapters
(CSV, In Memory Cart)

Try it out

Register for the first training
(40 seats)
https://bit.ly/2UhQKfG
Di., 27.08.2019, 09:00 Uhr –
Mi., 28.08.2019, 17:00 Uhr MESZ
Wiesbaden, AOE Headquarter

Blazing fast commerce experience layer
Open sourced with from
www.flamingo.me
@aoepeople
@danpoetz