Specialized in designing, implementing and maintaining solutions with traditional databases (Teradata) and with Big Data technologies (Hadoop, MongoDB, Spark, ...).
Objectives : - To build smart data-driven application - To deliver business value and accelerate time to market - To analyze data to extract real and signifiant information for strategic business decision - To lead agile projects in order to optimize flexibility and productivity - To teach development processes and good practice
Certified Professional for Requirements Engineering Certified Professional Scrum Master I (Scrum.org) MongoDB Certified Developer
Microservices are great, problems arise when you start to have two of them and when you want to deal with data :)
Pun aside, data and state is a big subject that is largely ignored when discussing Microservices.
- Conundrum #1 : What is the aimed data architecture in a perfect Microservices architecture?
- Conundrum #2 : How do you share state between instances of a given Microservice in a stateless 12 factor approach?
- Conundrum #3 : how to echange state between Microservices that must remain independent?
- Conundrum #4 : how do I go from my brownfield database to a fleet of Microservices IRL without a Big Bang? Conundrum #5 : with many Microservices touching many data sets, how do I guarantee uniformed security (GDPR anyone)?
And the list goes on. This presentation is an opinionated answer to these questions. And yes we do demo these concepts.