Creditas: Orchestrating Hundreds of MS with Camunda

In this lecture at Camunda Summit 2022, Janderson Silva taught how Creditas, a Brazilian fintech company, uses Camunda to orchestrate the business flows of its main products and also deals with challenges of scale and microservices that serve thousands of customers.

He talked about how mapped business flows, defined the architecture and created abstraction layers on top of Camunda to facilitate integration with the platform. In addition to show about Creditas service scaling and orchestration challenges.

Transcript

1. CCS 2022 #CamundaSummit
2. Document classification #CamundaSummit Public Orchestrating Hundreds of MS with Camunda
3. an A company focused on reducing the interest rates Brazilians were paying on loans.
4. Sergio Furio Founder & CEO Spanish who worked in New York. In 2010, he heard about the huge interest rates in Brazil. In March 2012 he moved to Brazil and set up a company called Bankfacil
6. Interest rates
7. an Practicing our own interest rates 2017
9. Interest rates
11. https://ir.creditas.com/ir/financial-information/creditas-financial-results-q4-2021
12. 2020 > US$ 1Bi Robust
13. 2020 > US$ 1Bi Sustainable
15. Brazil (HQ) Mexico Spain
16. 7 Orchestrating Hundreds of MS with Camunda 4600+ Crew members 2012 Crew member 2022
17. 3313 Orchestrating Hundreds of MS with Camunda ~110 Deploys 30d Deploys/day
18. Architecture
19. “you shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile” Fowler, 2015 Orchestrating Hundreds of MS with Camunda
20. Business process inside monolithic application without visibility to business teams, only engineering knows and work on it
21. Business process outside monolithic application business teams contributions, but still without visibility, hard to maintaining on engineering
22. Splitting the monolithic application into microservices microservices for functionality is not a good idea
23. Business Process Manager + Monolith + Microservices Low cycle time, high MTTR
24. We are facing many troubles, high coupling, low cohesion, single point of failure Orchestrating Hundreds of MS with Camunda
25. Three main decisions Orchestrating Hundreds of MS with Camunda
26. Camunda Bounded Contexts Features Don't reinvent the wheel! Use Camunda Create new microservices by bounded context Stop creating microservices for single functionality
27. Business Process orchestration using Camunda BPMN designed by business people, reviewed and tested by developers
33. Business Process Model and Notation (BPMN) bpmn.org
34. Microservices was pooling Journey-v2/Camunda APIs Easy for business, hard for engineering: A single point of failure
35. Complexity growing fast
36. Complexity growing very fast
37. Publishing events to Kafka Decoupling Asynchronous communication More resilience for the ecosystem
40. Microservices listening Journey-v2/Camunda events Both possibilities: orchestration and choreography
41. Bounded Context A Bounded Context B Bounded Context C Bounded Context Z
42. This approach allowed us to orchestrate the entire microservices ecosystem! Orchestrating Hundreds of MS with Camunda
43. an Next steps 2022
44. We are discussing right now if we are going to use database federation or sharding! Orchestrating Hundreds of MS with Camunda
45. Database Federation approach Home Equity process instances Auto Equity process instances Product N process instances
46. Database Sharding approach Product A, B, C process instances Product D, E, F process instances Product G, H, I process instances
47. an Lessons learned
48. To maintain a Saas it is necessary to treat it as a product and not as a generic tool
49. It’s difficult to maintain the approach of creating your own Saas, it is easier to follow the approach of using Camunda as a library in each of your services or using Camunda Cloud as a central orchestrator
50. It’s not a good idea to maintain a saas via inner source
51. an Further reading
53. Thanks! For more info: https://www.creditas.com https://www.linkedin.com/in/janderson-silva
54. Questions?