[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"profile-en":3,"$f1q30og2a68cbk":74},{"fullName":4,"role":5,"headline":6,"intro":7,"about":8,"essay":9,"location":10,"currentPosition":11,"availability":12,"email":13,"phone":14,"whatsappUrl":15,"linkedinUrl":16,"githubUsername":17,"cvUrl":18,"photoUrl":19,"domains":20,"experiences":37,"testimonials":63,"updatedAt":72,"translations":73},"Marc Ariel Oka","Senior Software Engineer · Fullstack","I design and build software products, *from the system to the experience.*","Senior fullstack software engineer based in Abidjan. I design and build complete web and mobile applications, with a frontend specialisation and projects in artificial intelligence, automation and machine learning. Founder of FACTio, an invoicing SaaS in production.","I am a fullstack software engineer. I design and build complete applications, web and mobile: architecture, business logic, APIs, databases and interfaces.\n\n## How I approach a problem\n\nBefore writing code, I try to understand the business: who uses the tool, what constraints they work under, what absolutely has to work. A good part of my work is turning scattered processes — spreadsheets, WhatsApp threads, manual data entry — into reliable, clear applications.\n\n## What I do\n\nI work on the backend as much as on the frontend, mainly with Laravel, Vue.js, Nuxt and Flutter. I am currently a senior fullstack developer at Flot, with solid frontend experience. Outside that role, I work on artificial intelligence, automation and machine learning projects in Python, sometimes with models running locally through Ollama.\n\n## FACTio, my product\n\nI designed, built and shipped FACTio, my own SaaS for invoicing and payment tracking, aimed at freelancers and small businesses. I keep evolving it based on what its users need.\n\n## What I want to go deeper into\n\nAI engineering and machine learning applied to real products, the architecture of applications that need to last, and the quality of interfaces on complex user journeys.","I work across the whole of an application, web or mobile: its architecture, business logic, APIs, data and interfaces. I am currently a senior fullstack developer at Flot.\n\nWhat I am most passionate about is applied research in artificial intelligence: understanding how models work, putting them to the test on real problems and seeing what holds up in production. I explore agents, automation and machine learning, often with models running locally.\n\nI am also building [FACTio](\u002Fprojets\u002Ffactio), my own invoicing SaaS, now in production. Along the way, I have designed platforms such as [Perafind](\u002Fprojets\u002Fperafind), [DS-Accessories](\u002Fprojets\u002Fds-accessories) and [Digifop](\u002Fprojets\u002Fdigifop) for AGEFOP.","Abidjan, Côte d’Ivoire","Senior Fullstack Developer at Flot","Available for projects, locally and internationally","okaamarc@gmail.com","+225 05 76 10 52 39","https:\u002F\u002Fwa.me\u002F2250576105239","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmarc-ariel-oka\u002F","Marc-Ariel-Oka","\u002Fcv\u002Fmarc-ariel-oka-cv.pdf","\u002Fimages\u002Fmarc-ariel-oka.webp",[21,25,29,33],{"title":22,"tools":23,"problem":24},"Fullstack Software Engineering","Laravel · PHP · PostgreSQL · MySQL · Docker","Designing a complete application — architecture, business logic, API, database, interface — and evolving it in production.",{"title":26,"tools":27,"problem":28},"Advanced Frontend","Vue.js · Nuxt · TypeScript · Tailwind CSS · Flutter","Fast, readable interfaces, including on complex journeys, on the web as well as on mobile.",{"title":30,"tools":31,"problem":32},"AI Engineering & Automation","Python · Ollama · Agents IA","Automating repetitive tasks and connecting language models to your data — locally when confidentiality requires it.",{"title":34,"tools":35,"problem":36},"Machine Learning","Python","Designing and integrating models when hand-written rules are no longer enough.",[38,44,49,54,59],{"title":39,"period":40,"company":41,"current":42,"description":43},"Senior Fullstack Developer","2025 — present","Flot",true,"Implementing designs and building high-performance interfaces, creating APIs and integrating third-party services. Leading integrations and the production releases of the web and mobile applications.",{"title":45,"period":46,"company":47,"description":48},"Fullstack Developer","2025","Emeryte","Building internal software: a money transfer application and a sports betting management platform.",{"title":50,"period":51,"company":52,"description":53},"Fullstack & IoT Developer","2024 — 2025","Orange Digital Center","Selected for the Orange Digital Academy programme to design an innovative project combining IoT and artificial intelligence.",{"title":55,"period":56,"company":57,"description":58},"Web Developer","2022 — 2024","In-novation","Building a platform to manage paid assignments for influencers and content creators.",{"title":60,"period":61,"company":57,"description":62},"Web Developer Intern","2022","Contributed to building an e-commerce template generator for small retailers.",[64,68],{"role":65,"quote":66,"author":67},"Project Manager — Perafind","Marc Ariel Oka est un travailleur vraiment sérieux. En travaillant avec lui sur Perafind, j'ai apprécié son dévouement et sa passion pour son métier de développeur. Dynamique et ouvert d'esprit, il sait piloter un projet et aime le travail bien fait. Je suis très satisfait de collaborer avec lui.","Franck Joris Anael Ahoussi",{"role":69,"quote":70,"author":71},"CEO — DS-Accessories","Un travail vraiment impeccable, rien à redire.","Michèle Samuela Koumi Ntakpe","2026-11-05T20:00:57.915801+00:00",{},{"post":75,"html":105,"toc":106,"previous":127,"next":130},{"id":76,"slug":77,"title":78,"excerpt":79,"content":80,"coverUrl":81,"coverAlt":81,"status":82,"featured":42,"readingMinutes":83,"lang":84,"translated":42,"seoTitle":85,"seoDescription":86,"translations":87,"publishedAt":88,"updatedAt":89,"category":90,"tags":95},"5e161f9f-3b6e-49a2-b163-177425d257d2","monolithe-ou-microservices-ce-qu-une-pme-devrait-vraiment-choisir","Monolith or Microservices: What a Small Business Should Really Choose","Microservices are the stuff of dreams. But even Amazon and Shopify have chosen monolith for some systems. Here’s how to decide without following fashion.","At the start of a project, one question keeps coming up: \"Should we go with microservices, like Netflix?\"\n\nIt's a fair question. But Netflix has thousands of engineers and hundreds of millions of users. Your small business may have three developers and a few thousand customers. Copying a giant's architecture is a bit like buying a bus to commute alone: it runs, but it's expensive to maintain.\n\nSo, monolith or microservices? Here's how I see it, along with what the big companies have learned themselves.\n\n## The three options, in plain words\n\n**The monolith**: the whole application is a single program, deployed in one piece, with a single database. It's the starting point of most Laravel, Rails or Django projects.\n\n**Microservices**: the application is split into small independent services (billing, payments, notifications…), each with its own database, talking to each other over the network.\n\n**The modular monolith**: a single program, but organised into business modules with strict boundaries. Each module owns its data and can only be reached through a clear interface.\n\n| | Classic monolith | Modular monolith | Microservices |\n| --- | --- | --- | --- |\n| Deployment | One | One | One per service |\n| Speed at the start | Very fast | Fast | Slow |\n| Infrastructure cost | Low | Low | High |\n| DevOps skills needed | Basic | Basic | Advanced |\n| Main risk | Tangled code as it grows | Discipline to maintain | Network and data complexity |\n| Best for | Prototype, small team | Small business, growing startup | Large independent teams |\n\n## What the big companies learned\n\n**Martin Fowler, 2015.** One of the authors who popularised microservices makes a simple observation: almost all successful microservice stories started with a monolith that got too big and was broken up. Conversely, systems built as microservices from day one almost always end up in serious trouble.\n\n**Shopify, 2019.** Over 1,000 developers work on the same Ruby on Rails codebase. When it became hard to manage, Shopify didn't rush to microservices. The team judged they would solve some problems but create others: more pipelines to maintain, latency on every network call, data harder to get at. They chose a modular monolith, split by business domain (orders, shipping, billing), with a tool that blocks forbidden calls between modules.\n\n**Amazon Prime Video, 2023.** The team monitoring video stream quality merged its distributed components into a single process. Reported result: over 90% savings on that tool's infrastructure, and better ability to scale.\n\nBe careful not to over-generalise. This is one tool, not Prime Video's entire architecture. And microservices remain relevant when an organisation has many teams that each need to ship independently. The lesson is that architecture is chosen to fit the problem, not the trend.\n\n## How to choose: five questions to ask\n\n1. **How many developers will work on it?** Microservices first solve an organisational problem: letting several teams ship without stepping on each other's toes. With a team of three, that problem doesn't exist.\n2. **Does one part of the system have very different needs?** For example, heavy image processing while the rest of the app is lightweight. That's often the only good reason to pull a piece out.\n3. **Do you have the DevOps skills?** With microservices, you deploy, monitor and debug dozens of moving parts. Without solid continuous integration, centralised logs and request tracing, every bug becomes an investigation.\n4. **Is your business domain already stable?** Splitting too early means freezing boundaries you don't understand well yet. Moving them later costs far more between two services than between two folders.\n5. **What's your infrastructure budget?** Each service has its own server or container, database and monitoring. The bill climbs fast.\n\n## My recommendation for a small business or startup\n\nStart with a **modular monolith**. You keep the simplicity of a single deployment, and you prepare for what comes next.\n\nIn practice, on a Laravel project, I organise the code by business domain rather than by file type:\n\n```\napp\u002F\n└── Modules\u002F\n    ├── Billing\u002F\n    │   ├── Models\u002F\n    │   ├── Actions\u002F\n    │   ├── Events\u002F\n    │   └── BillingService.php   ← the only way in\n    ├── Customers\u002F\n    └── Payments\u002F\n```\n\nFour rules are enough to make it hold over time:\n\n- **Each module owns its tables.** The Payments module never reads Billing's tables directly: it goes through the Billing service.\n- **Modules communicate through interfaces or events.** For example, Payments publishes \"PaymentReceived\", and Billing marks the invoice as paid.\n- **Boundaries are checked automatically.** An architecture test (with Pest, for example) fails if a module imports another module's internal code.\n- **A service is only extracted for a real reason.** A heavy workload (document processing, bulk messaging) can move to a separate service or worker the day it slows everything else down. Thanks to the boundaries already in place, the extraction is simple.\n\nThis approach keeps every door open. If your business takes off tomorrow and the team grows to thirty developers, each module can become a microservice without rewriting everything.\n\n## In short\n\nMicroservices are not a higher level. They're an answer to a specific problem: many teams that each need to ship on their own. If you don't have that problem yet, you pay the price of the solution without getting its benefits.\n\nA well-organised monolith is not old-fashioned. It's often the most mature choice.\n\nUnsure about the architecture of your next project, or is your current application getting hard to evolve? [Get in touch](https:\u002F\u002Fwww.marc-oka.com\u002Fcontact) and let's talk.\n\n---\n\n### Sources\n\n- [MonolithFirst](https:\u002F\u002Fwww.martinfowler.com\u002Fbliki\u002FMonolithFirst.html), Martin Fowler, June 3, 2015.\n- [Deconstructing the Monolith: Designing Software that Maximizes Developer Productivity](https:\u002F\u002Fshopify.engineering\u002Fblogs\u002Fengineering\u002Fdeconstructing-monolith-designing-software-maximizes-developer-productivity), Kirsten Westeinde, Shopify Engineering, February 21, 2019.\n- [Reduce costs by 90% by moving from microservices to monolith: Amazon internal case study raises eyebrows](https:\u002F\u002Fdevclass.com\u002F2023\u002F05\u002F05\u002Freduce-costs-by-90-by-moving-from-microservices-to-monolith-amazon-internal-case-study-raises-eyebrows\u002F), Tim Anderson, DevClass, May 5, 2023.","","published",5,"en","Monolith or Microservices: The Right Choice for Small Businesses","Microservices aren’t a must. What Amazon and Shopify learned, and the architecture that really fits a small business or startup.",{},"2026-11-20T09:40:00+00:00","2026-11-20T09:38:08.557181+00:00",{"id":91,"name":92,"slug":93,"description":94},"afb42366-e014-41b2-a657-8417ec7d99ac","Software architecture","architecture-logicielle","Software engineering, design and architecture decisions.",[96,99,102],{"id":97,"name":98,"slug":98},"40d216a9-9af7-4374-830b-39a0babd9f18","architecture",{"id":100,"name":101,"slug":101},"9b93b346-f8d8-449f-b79d-93e843d645cd","microservice",{"id":103,"name":104,"slug":104},"aa3945b8-53a0-4a51-afc6-9fc8237b424d","monolithe","\u003Cp>At the start of a project, one question keeps coming up: « Should we go with microservices, like Netflix? »\u003C\u002Fp>\n\u003Cp>It’s a fair question. But Netflix has thousands of engineers and hundreds of millions of users. Your small business may have three developers and a few thousand customers. Copying a giant’s architecture is a bit like buying a bus to commute alone: it runs, but it’s expensive to maintain.\u003C\u002Fp>\n\u003Cp>So, monolith or microservices? Here’s how I see it, along with what the big companies have learned themselves.\u003C\u002Fp>\n\u003Ch2 id=\"the-three-options-in-plain-words\">The three options, in plain words\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>The monolith\u003C\u002Fstrong>: the whole application is a single program, deployed in one piece, with a single database. It’s the starting point of most Laravel, Rails or Django projects.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Microservices\u003C\u002Fstrong>: the application is split into small independent services (billing, payments, notifications…), each with its own database, talking to each other over the network.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The modular monolith\u003C\u002Fstrong>: a single program, but organised into business modules with strict boundaries. Each module owns its data and can only be reached through a clear interface.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>\u003C\u002Fth>\n\u003Cth>Classic monolith\u003C\u002Fth>\n\u003Cth>Modular monolith\u003C\u002Fth>\n\u003Cth>Microservices\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Deployment\u003C\u002Ftd>\n\u003Ctd>One\u003C\u002Ftd>\n\u003Ctd>One\u003C\u002Ftd>\n\u003Ctd>One per service\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Speed at the start\u003C\u002Ftd>\n\u003Ctd>Very fast\u003C\u002Ftd>\n\u003Ctd>Fast\u003C\u002Ftd>\n\u003Ctd>Slow\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Infrastructure cost\u003C\u002Ftd>\n\u003Ctd>Low\u003C\u002Ftd>\n\u003Ctd>Low\u003C\u002Ftd>\n\u003Ctd>High\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>DevOps skills needed\u003C\u002Ftd>\n\u003Ctd>Basic\u003C\u002Ftd>\n\u003Ctd>Basic\u003C\u002Ftd>\n\u003Ctd>Advanced\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Main risk\u003C\u002Ftd>\n\u003Ctd>Tangled code as it grows\u003C\u002Ftd>\n\u003Ctd>Discipline to maintain\u003C\u002Ftd>\n\u003Ctd>Network and data complexity\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Best for\u003C\u002Ftd>\n\u003Ctd>Prototype, small team\u003C\u002Ftd>\n\u003Ctd>Small business, growing startup\u003C\u002Ftd>\n\u003Ctd>Large independent teams\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Ch2 id=\"what-the-big-companies-learned\">What the big companies learned\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Martin Fowler, 2015.\u003C\u002Fstrong> One of the authors who popularised microservices makes a simple observation: almost all successful microservice stories started with a monolith that got too big and was broken up. Conversely, systems built as microservices from day one almost always end up in serious trouble.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Shopify, 2019.\u003C\u002Fstrong> Over 1,000 developers work on the same Ruby on Rails codebase. When it became hard to manage, Shopify didn’t rush to microservices. The team judged they would solve some problems but create others: more pipelines to maintain, latency on every network call, data harder to get at. They chose a modular monolith, split by business domain (orders, shipping, billing), with a tool that blocks forbidden calls between modules.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Amazon Prime Video, 2023.\u003C\u002Fstrong> The team monitoring video stream quality merged its distributed components into a single process. Reported result: over 90% savings on that tool’s infrastructure, and better ability to scale.\u003C\u002Fp>\n\u003Cp>Be careful not to over-generalise. This is one tool, not Prime Video’s entire architecture. And microservices remain relevant when an organisation has many teams that each need to ship independently. The lesson is that architecture is chosen to fit the problem, not the trend.\u003C\u002Fp>\n\u003Ch2 id=\"how-to-choose-five-questions-to-ask\">How to choose: five questions to ask\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>How many developers will work on it?\u003C\u002Fstrong> Microservices first solve an organisational problem: letting several teams ship without stepping on each other’s toes. With a team of three, that problem doesn’t exist.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Does one part of the system have very different needs?\u003C\u002Fstrong> For example, heavy image processing while the rest of the app is lightweight. That’s often the only good reason to pull a piece out.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Do you have the DevOps skills?\u003C\u002Fstrong> With microservices, you deploy, monitor and debug dozens of moving parts. Without solid continuous integration, centralised logs and request tracing, every bug becomes an investigation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Is your business domain already stable?\u003C\u002Fstrong> Splitting too early means freezing boundaries you don’t understand well yet. Moving them later costs far more between two services than between two folders.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>What’s your infrastructure budget?\u003C\u002Fstrong> Each service has its own server or container, database and monitoring. The bill climbs fast.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2 id=\"my-recommendation-for-a-small-business-or-startup\">My recommendation for a small business or startup\u003C\u002Fh2>\n\u003Cp>Start with a \u003Cstrong>modular monolith\u003C\u002Fstrong>. You keep the simplicity of a single deployment, and you prepare for what comes next.\u003C\u002Fp>\n\u003Cp>In practice, on a Laravel project, I organise the code by business domain rather than by file type:\u003C\u002Fp>\n\u003Cfigure class=\"code-block\">\u003Cpre class=\"shiki github-light\" style=\"background-color:#fff;color:#24292e\" tabindex=\"0\">\u003Ccode class=\"language-text\">\u003Cspan class=\"line\">\u003Cspan>app\u002F\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>└── Modules\u002F\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>    ├── Billing\u002F\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>    │   ├── Models\u002F\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>    │   ├── Actions\u002F\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>    │   ├── Events\u002F\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>    │   └── BillingService.php   ← the only way in\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>    ├── Customers\u002F\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan>    └── Payments\u002F\u003C\u002Fspan>\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Ffigure>\u003Cp>Four rules are enough to make it hold over time:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Each module owns its tables.\u003C\u002Fstrong> The Payments module never reads Billing’s tables directly: it goes through the Billing service.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Modules communicate through interfaces or events.\u003C\u002Fstrong> For example, Payments publishes « PaymentReceived », and Billing marks the invoice as paid.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Boundaries are checked automatically.\u003C\u002Fstrong> An architecture test (with Pest, for example) fails if a module imports another module’s internal code.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A service is only extracted for a real reason.\u003C\u002Fstrong> A heavy workload (document processing, bulk messaging) can move to a separate service or worker the day it slows everything else down. Thanks to the boundaries already in place, the extraction is simple.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This approach keeps every door open. If your business takes off tomorrow and the team grows to thirty developers, each module can become a microservice without rewriting everything.\u003C\u002Fp>\n\u003Ch2 id=\"in-short\">In short\u003C\u002Fh2>\n\u003Cp>Microservices are not a higher level. They’re an answer to a specific problem: many teams that each need to ship on their own. If you don’t have that problem yet, you pay the price of the solution without getting its benefits.\u003C\u002Fp>\n\u003Cp>A well-organised monolith is not old-fashioned. It’s often the most mature choice.\u003C\u002Fp>\n\u003Cp>Unsure about the architecture of your next project, or is your current application getting hard to evolve? \u003Ca href=\"https:\u002F\u002Fwww.marc-oka.com\u002Fcontact\" target=\"_blank\" rel=\"noopener noreferrer\">Get in touch\u003C\u002Fa> and let’s talk.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3 id=\"sources\">Sources\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.martinfowler.com\u002Fbliki\u002FMonolithFirst.html\" target=\"_blank\" rel=\"noopener noreferrer\">MonolithFirst\u003C\u002Fa>, Martin Fowler, June 3, 2015.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fshopify.engineering\u002Fblogs\u002Fengineering\u002Fdeconstructing-monolith-designing-software-maximizes-developer-productivity\" target=\"_blank\" rel=\"noopener noreferrer\">Deconstructing the Monolith: Designing Software that Maximizes Developer Productivity\u003C\u002Fa>, Kirsten Westeinde, Shopify Engineering, February 21, 2019.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdevclass.com\u002F2023\u002F05\u002F05\u002Freduce-costs-by-90-by-moving-from-microservices-to-monolith-amazon-internal-case-study-raises-eyebrows\u002F\" target=\"_blank\" rel=\"noopener noreferrer\">Reduce costs by 90% by moving from microservices to monolith: Amazon internal case study raises eyebrows\u003C\u002Fa>, Tim Anderson, DevClass, May 5, 2023.\u003C\u002Fli>\n\u003C\u002Ful>\n",[107,111,114,117,120,123],{"id":108,"text":109,"level":110},"the-three-options-in-plain-words","The three options, in plain words",2,{"id":112,"text":113,"level":110},"what-the-big-companies-learned","What the big companies learned",{"id":115,"text":116,"level":110},"how-to-choose-five-questions-to-ask","How to choose: five questions to ask",{"id":118,"text":119,"level":110},"my-recommendation-for-a-small-business-or-startup","My recommendation for a small business or startup",{"id":121,"text":122,"level":110},"in-short","In short",{"id":124,"text":125,"level":126},"sources","Sources",3,{"slug":128,"title":129},"de-l-automatisation-a-l-autonomie-ce-que-les-agents-ia-changent-pour-une-entrepr","From Automation to Autonomy: What AI Agents Change for a Business",null]