Download to read offline
Uploaded byQuentin Adam
Problems you’ll face in the Microservices World: Configuration, Authentication … - DevOpsCon Munich 2017
The document discusses various challenges in the microservice architecture, including issues related to authentication, communication, and configuration. It emphasizes the importance of a robust system for managing services and highlights tools such as message brokers and event sourcing that can aid in this process. The author also advocates for a developer-centric approach to architecture, encouraging agility and innovation in software design.
More Related Content
Similar to Problems you’ll face in the Microservices World: Configuration, Authentication … - DevOpsCon Munich 2017
More from Quentin Adam
Problems you’ll face in the Microservices World: Configuration, Authentication … - DevOpsCon Munich 2017
- 1. Problems in themicroservice world: Authentication, communication, configuration and boundaries Quentin ADAM - @waxzce
- 2. Who am I? Quentin ADAM from the Clever Cloud @waxzce on twitter – github- soundcloud – instagram ….
- 3. My day today work : , the IT automation company
- 4. Keep your appsonline. made with node.js, scala, java, ruby, php, python, go… Cloud & on premise
- 5. And learn alot of things about your code, apps, and good/bad design…
- 6. Give back tothe community NEVER GONNA LET YOU DOWN clever-cloud.com
- 7. The beginning How CleverCloud start? How the roadmap was define.
- 8.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16. Architecture as aplayground Lego FTW
- 17.
- 18.
- 19. Server -> Server •Authenticated • Encrypted • Auditable/logged 🔪
- 20.
- 21. Routing is aproblem
- 22.
- 23.
- 24.
- 25.
- 26. Messages brokers • RabbitMQ •FR: https://www.youtube.com/watch?v=VBUQXM96hpw • EN: https://www.youtube.com/watch?v=15mzY2MfDgM • Kafka • Redis? • 0MQ? • Warp10 / time series DB📬
- 27. Migrate to eventsource?
- 28. The right size? Whatis the boundaries of a microservice
- 29.
- 30. Beware of (massive)RPC (Remote Procedure Call)
- 31. Network is twoproblems: Fragile and Slow
- 32. 📦 Micro servicesis not Workload Distribution 👁 akka, project orleans, Erlang OTP, hadoop…
- 33. One service dohave to actually provide a service by itself
- 34.
- 35. Micro service creatingtoo much lib?
- 36. Why theses twofunctions are in the same services? Or can I 👁 it?
- 37. Does we havea common data store?
- 38. Does this featuresneed the same scaling agenda?
- 39.
- 40.
- 41.
- 42. Zk, etcd, consul…So many possibilities
- 43. Reconfigure at runtime? Hotreloading or live configuration? https://www.clever-cloud.com/blog/engineering/2017/07/24/hot- reloading-configuration-why-and-how/
- 44. Simpler way, neverchange on runtime Immutable infrastructure (FR) https://www.youtube.com/watch?v=WrZCbgQsPVU
- 45. Agnostic solution: Environmentvariable
- 46.
- 47. No over engineeringon configuration, when you need to configure the configuration injector, you are too far 🖇
- 48. Who the hellare you? Distribute Authentication
- 49.
- 50.
- 51. Shared data repository Redis Service A(php) Service C (java) Service B (nodejs)
- 52. Authentication using aproxy Request Reverse Proxy + Database call + Business code + Authentication Service A Service B Service C Authenticated request with user identity data
- 53. Central API callto authenticate request Request Via reverse proxy Service A Service B Service C Authentification API
- 54. We need moretools 👁 🔧 🔩 ⛏ ⚒ 👁
- 55.
- 56.
- 57.
- 58. Keep hackable andpluggable playground to enforce innovations
- 59.
- 60. Clean legacy codeon regular basis Why and how bookkeepers f***d up IT FR https://www.youtube.com/watch?v=0ip1FoBsLB4 EN https://www.youtube.com/watch?v=OngWRJ8txps
- 61.
- 62. No dogma, fulldeveloper hapiness oriented architecture
- 63. Thank you find meon twitter @waxzce Gift coupon for clever-cloud.com: devopsCon17
Editor's Notes
- #40 Exemple à Clever Cloud
- #52 The first idea to many developer is to share the access to a database with the session data (memcached or redis), and read access to the ACL database (SQL or something) Issues on this : - change to the data model require to edit all the series - impose rude connection and pooling to the databases, which is an OPS problem - creating a SPOF - impose lots of code rewriting in each micro service
- #53 Good part is : - centralisation of authentication and code related to it Issues : - Very complicated to mock on developer laptop : you need to launch the proxy on dev computer - Security vision is optimistic - The user infos add by the proxys aren’t requested by service, so it’s standard or convention between proxy and service - proxy is a spot mix several mission on the proxy : routing, load balancing, authentication, session hydratation… PERFORMANCES
- #54 Central authentication API called by services In this architecture, service take request directly and call an API to authenticate the request, serializing verb, resources and headers and asking for extra info they will need (user infos), the authentication API respond authentication and user info requested by the service. Good parts : - easy to mock and work on developer part, no need to start on developer computer - centralisation of the authentication - security is better handled and there is less possibility to breach the system spoofing requests - services request additional infos, more simple to do Issues : - authentication API is a spof
- #57 Signature