[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technology-en-symfony":3,"technology-projects-en-symfony":30,"mdc--so9i63-key":31},{"id":4,"title":5,"category":6,"content":7,"description":8,"extension":9,"faq":10,"icon":17,"links":18,"meta":24,"projects":25,"since":26,"stem":27,"updated":28,"__hash__":29},"technologies_en\u002Fen\u002Ftechnologies\u002Fsymfony.yml","Symfony","backend","Symfony is a PHP framework I use in my commercial work on a ticketing platform serving Formula 1, MotoGP, EICMA and EuroLeague events. My work covers both customer-facing purchase flows and internal administration tools.\n\n## What I work on\n\n- **Checkout** — cart behavior, seat selection, order confirmation and ticket delivery.\n- **Payments** — integrations with providers such as Stripe and Dalenys.\n- **Accounts and administration** — customer profiles, order history and tools for managing events and orders.\n- **External services** — seat-map solutions and third-party APIs in the purchase flow.\n\n## What ticketing demands\n\nWhen sales open, a platform must handle changes in demand while keeping orders and seat availability consistent. That makes transaction boundaries, payment states and error handling especially important. A fast page is useful only if the customer can complete the correct purchase.\n\n## Symfony and Laravel in my work\n\nI work with both frameworks. Existing architecture, team conventions and integrations influence the choice more than a fixed division between enterprise and smaller products. On an established Symfony application, I focus on changes that can be tested, reviewed and maintained through future releases.\n","Symfony development for ticketing platforms: checkout, payment integrations, user accounts and administration tools for event sales.","yml",[11,14],{"label":12,"content":13},"What kind of Symfony projects have you worked on?","My commercial work includes a ticketing platform for Formula 1, MotoGP, EICMA and EuroLeague events, covering checkout, payment integrations and administration tools.",{"label":15,"content":16},"Can you work on an existing Symfony application?","Yes. I start by understanding the architecture and release process, then identify changes and tests needed to extend the application safely.","i-simple-icons-symfony",[19],{"label":20,"to":21,"color":22,"icon":23},"symfony.com","https:\u002F\u002Fsymfony.com","neutral","i-heroicons-arrow-top-right-on-square",{},[],"2019","en\u002Ftechnologies\u002Fsymfony","2026-09-20","I8IiYbUfTERLBQRwjdgunfHlFSvBRL7HeQOsepcxglY",[],{"data":32,"body":33},{},{"type":34,"children":35},"root",[36,44,51,97,103,108,114],{"type":37,"tag":38,"props":39,"children":40},"element","p",{},[41],{"type":42,"value":43},"text","Symfony is a PHP framework I use in my commercial work on a ticketing platform serving Formula 1, MotoGP, EICMA and EuroLeague events. My work covers both customer-facing purchase flows and internal administration tools.",{"type":37,"tag":45,"props":46,"children":48},"h2",{"id":47},"what-i-work-on",[49],{"type":42,"value":50},"What I work on",{"type":37,"tag":52,"props":53,"children":54},"ul",{},[55,67,77,87],{"type":37,"tag":56,"props":57,"children":58},"li",{},[59,65],{"type":37,"tag":60,"props":61,"children":62},"strong",{},[63],{"type":42,"value":64},"Checkout",{"type":42,"value":66}," — cart behavior, seat selection, order confirmation and ticket delivery.",{"type":37,"tag":56,"props":68,"children":69},{},[70,75],{"type":37,"tag":60,"props":71,"children":72},{},[73],{"type":42,"value":74},"Payments",{"type":42,"value":76}," — integrations with providers such as Stripe and Dalenys.",{"type":37,"tag":56,"props":78,"children":79},{},[80,85],{"type":37,"tag":60,"props":81,"children":82},{},[83],{"type":42,"value":84},"Accounts and administration",{"type":42,"value":86}," — customer profiles, order history and tools for managing events and orders.",{"type":37,"tag":56,"props":88,"children":89},{},[90,95],{"type":37,"tag":60,"props":91,"children":92},{},[93],{"type":42,"value":94},"External services",{"type":42,"value":96}," — seat-map solutions and third-party APIs in the purchase flow.",{"type":37,"tag":45,"props":98,"children":100},{"id":99},"what-ticketing-demands",[101],{"type":42,"value":102},"What ticketing demands",{"type":37,"tag":38,"props":104,"children":105},{},[106],{"type":42,"value":107},"When sales open, a platform must handle changes in demand while keeping orders and seat availability consistent. That makes transaction boundaries, payment states and error handling especially important. A fast page is useful only if the customer can complete the correct purchase.",{"type":37,"tag":45,"props":109,"children":111},{"id":110},"symfony-and-laravel-in-my-work",[112],{"type":42,"value":113},"Symfony and Laravel in my work",{"type":37,"tag":38,"props":115,"children":116},{},[117],{"type":42,"value":118},"I work with both frameworks. Existing architecture, team conventions and integrations influence the choice more than a fixed division between enterprise and smaller products. On an established Symfony application, I focus on changes that can be tested, reviewed and maintained through future releases."]