Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Microservices architecture pitfalls
Search
Mateusz Gajewski
March 07, 2015
Programming
1
210
Microservices architecture pitfalls
This is the talk about common pitfalls met while building scalable microservice architecture
Mateusz Gajewski
March 07, 2015
Tweet
Share
More Decks by Mateusz Gajewski
See All by Mateusz Gajewski
Modern java for decade-old problems
wendigo
0
140
3 kroki do tyłu, 2 lata w przód
wendigo
2
170
JDD - Dług techniczny
wendigo
2
1.2k
WJUG 2017: 4 lata rewolucji mikrousługowej w Allegro
wendigo
0
340
4 lata rewolucji mikrousługowej w Allegro
wendigo
2
800
Project Rubicon
wendigo
0
360
RxJava - Reactive extensions for the JVM
wendigo
1
300
Building distributed systems with OSS
wendigo
1
160
Scaling infrastructure beyond containers
wendigo
1
160
Other Decks in Programming
See All in Programming
ふつうの技術スタックでアート作品を作ってみる
akira888
0
460
PostgreSQLのRow Level SecurityをPHPのORMで扱う Eloquent vs Doctrine #phpcon #track2
77web
2
500
WindowInsetsだってテストしたい
ryunen344
1
240
第9回 情シス転職ミートアップ 株式会社IVRy(アイブリー)の紹介
ivry_presentationmaterials
1
280
Team operations that are not burdened by SRE
kazatohiei
1
310
Select API from Kotlin Coroutine
jmatsu
1
230
システム成長を止めない!本番無停止テーブル移行の全貌
sakawe_ee
1
160
明示と暗黙 ー PHPとGoの インターフェイスの違いを知る
shimabox
2
480
Flutterで備える!Accessibility Nutrition Labels完全ガイド
yuukiw00w
0
150
既存デザインを変更せずにタップ領域を広げる方法
tahia910
1
280
なぜ適用するか、移行して理解するClean Architecture 〜構造を超えて設計を継承する〜 / Why Apply, Migrate and Understand Clean Architecture - Inherit Design Beyond Structure
seike460
PRO
3
750
NPOでのDevinの活用
codeforeveryone
0
790
Featured
See All Featured
A better future with KSS
kneath
239
17k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
161
15k
The Art of Programming - Codeland 2020
erikaheidi
54
13k
We Have a Design System, Now What?
morganepeng
53
7.7k
Thoughts on Productivity
jonyablonski
69
4.7k
The Pragmatic Product Professional
lauravandoore
35
6.7k
Done Done
chrislema
184
16k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.4k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Large-scale JavaScript Application Architecture
addyosmani
512
110k
Art, The Web, and Tiny UX
lynnandtonic
299
21k
Music & Morning Musume
bryan
46
6.6k
Transcript
Microservices architecture pitfalls WJUG meeting ◦ march 2015 Mateusz Gajewski
Solutions Architect @ Allegro Twitter: @wendigo
About me given: I started working in Allegro in 2009
(5 mln AO, 50 devs) when: Allegro reached 40 mln AO, 400 devs then: I am Solutions Architect 2
Agenda • Microservices, microservices, microservices! ;) • Some challenges &
pitfalls: • Architectural, • Operational, • Organisational 3
Let’s go back in time to year 2012 4
5
Back then we wanted • agile development, • scalability, •
resilience, • lower costs, • hybrid cloud. 6
Basically SOA + JVM was an answer! 7
But our system was too BIG & too complex to
do it with existing enterprise solutions 8
s/Enterprise/OSS/g Solutions ;) 9
we’ve started to do *buzzword* 10
And now, literally everyone is doing microservices!!?? 11
Microservices by Fowler 12 Lots of *buzzwords* http://martinfowler.com/articles/microservices.html
SOA ≈ microservices? 13
microservices architecture ≈ fine-grained SOA − enterprise (commercial) sh*t ≈
highly scalable, distributed system 14
Distributed systems • concurrency of components, • independent failure of
components, • lack of a global clock. 15
The Eight Fallacies of Distributed Computing 16 by Peter Deutsch
1991
#1: Network is reliable 17
#2: Latency is zero 18
#3: Bandwidth is infinite 19
#4: Network is secure 20
#5: Topology doesn’t change 21
#6: There is one administrator 22
#7: Transport cost is zero 23
#8: Network is homogeneous 24
distributed systems are hard → microservices are much harder ;)
25
What have we learnt? 26
Act I: architectural constraints 27
CAP is not just theorem it’s reality against us 28
bye, bye ACID semantics 29
Long live BASE guarantees! Basically Available, Soft state, Eventually consistent
30
distributed transactions add complexity 31
it’s far cheaper to do compensation 32
33 http://bravenewgeek.com/you-cannot-have-exactly-once-delivery/
you need idempotent APIs and events sinks 34
35 choreography > orchestration
So we’ve built Hermes a.k.a circulatory system 36
network can be congested! 37
REST+JSON on top of HTTP/1.1 is fine 38
REST+JSON on top of HTTP/2.0 with TLS is finer 39
we don’t rely on network anymore net splits in public
clouds happens everytime! 40
we adopted antifragile organization 41
42
powerful tandem 43 + Reactive programming Circuit breaker pattern
you need to support non- native old services, clients and
systems 44
45
conclusion: constant architecture improvement 46
47 Act II: operational troubles
creating new service should be instant! 48
49
automation with gradle & axions 50
51
so now we’ve got over 1800 repositories grouped under 250
projects 52
all with CI, code quality checks, security checks, integrated with
sonar & artefact repository 53
but what with services upgrades? 54
we’ve initially built our own service stack … and it
was ok - for a while 55
now we are extending spring-boot with so called andamio project
56
rapid deployments integrated with CI/CD environment and canary tests are
must-have 57
war files ▾ scp + puppet ▾ golden images ▾
docker (immutable images) ▾ 58
frequency of changes → automated monitoring, logging &
operational insights 59
graphite statsd cabot tessera kibana logstash zabbix newrelic selena pingdom
… 60
Monitoring As A Service + SLA Monitoring + 61
we need to build real-time anomaly detection soon 62
63 Act III: organizational shift
strategic DDD is good for splitting up monolith 64
but leave tactical DDD up to teams 65
huge polyglot hangover 66
acquiring distributed skills 67
you build it - you run it 68
coupling avoidance 69
please don’t audit me 70
distributed (micro) data curation 71
So after two years… 72
73
Final thoughts 74
75
76
77
Thanks! Any questions? Visit our blog: allegrotech.io Follow us on
twitter: @allegrotechblog Check our OSS projects: github.com/allegro And meetup group: meetup.com/allegrotech 78