Thunes is a B2B company that powers payments for the world’s fastest-growing businesses - from Southeast Asia's superapp Grab and Gig Economy giants, to Fintech leaders such as PayPal and Remitly.

With a single, simple connection, your business and customers can send payments to – and get paid in – every corner of the world. Instantly.

We support 79+ currencies, enable payments to 130 countries, and help you accept 300+ payment methods.

Thunes is headquartered in Singapore with regional offices in London, Paris, Shanghai, New York, Miami, Dubai, Barcelona, and Nairobi.

For more information, visit http://www.thunes.com

👔 Business: We produce electric vehicle (EV) smart chargers that can be remotely controlled from the MyWallbox site and Wallbox mobile app. Also, the chargers can take energy from the EV using them as a power source for the building.

⏱️ Challenge: Wallbox is growing super fast which makes us go an extra mile every day so we are ready to manage the active users increase. Also, the team is growing fast too so this challenges how everything is organized.

⚙️ Tech: We create and maintain services mostly based on Go and PHP. We also have some NodeJS old services just to maintain where we don't add new features. We are creating more new isolated services that come from a big legacy monolith. We go for an event-driven communication fully asynchronous that gives us reliability enough to deal with problems we might face in one of the services. We apply Hexagonal Architecture, DDD and Clean Code because we feel that is the way to have a good codebase that is easy to extend and to understand.

🤼 Team: I'm on the platform team. A one that is growing fast having already 12 members which 10 of them are backends. Our main purpose is maintaining the legacy monolith doing big refactors so gets easy to add new features, splitting part of it on new services, helping the TechOps team deal with our infrastructure, having proper monitoring and alerting in place so we catch any problem before our users.

⚡ Impact: From the backend team we have a huge impact on the company since any business logic of the chargers is inside our services ecosystem: remote charger actions, authorization, authentication, group of users management, charging metrics, user notifications, payments... I also have an impact on our team members mentoring some of them for the new architecture we are implementing.

I'm maintaining and developing new features for all payment (micro)services of Letgo which include Bump Ups, Subscriptions (We created this (micro)service when I was on Verticals squad), and payments (Apple, Google Play Store, and Stripe).

All the services are developed with PHP 7 and Symphony, most of them use No-SQL databases over DynamoDB, a few though have some RDS database with MariaDB.
We also have several Golang lambdas to handle some scheduled jobs and to react over events. Also, for the sake of speeding up some features, we've been implementing some features to other team projects made with Scala.

A part of the main projects I've been creating and maintaining a Golang CLI tool to help us with some fixes and maintenance that are needed to be applied to a big volume of data.
Also, I've been in charge of migrating two of our main services to Kubernetes: payments and bumps.

The devs in the squad are handling also part of our Terraform setup, so we can create and modify SQS queues, SNS subscriptions, filters... in a faster way.

The squad follows scrum and is formed for backends, sysadmins, iOS developers, Android developers, QAs, TPM, POs, and BIs.

I joined one of the squads in charge of preparing the app to be able to sell new kind of products and to handle the new subscriptions system that works with Google and Apple purchases.

The squad follows scrum and is formed for 2-4 backends, 1 sysadmin, 2 iOS developers, 2 Android developers, 1 QA, 1 TPM, and 1 PO.

We use PHP 7, MySQL for the write model, Solr for the projections of the read model, Symfony 3, Doctrine... we design all the services following DDD and CQRS.
To communicate between (micro)services of our squad and the ones of other squads we use domain events, through AWS with SQS and SNS, so we get reactive systems with a low number of direct HTTP calls.
We test our API's and consumers with Behat and our code with PHPUnit.

We also use Golang to develop small lambdas and processes to handle and manipulate data.

Backend Developer in one of the company teams in charge of two projects.

The first project is based on PHP and Node JS, and we do unit tests over PHPSpec and PHPUnit.
It's a background checking site, operative only in the USA.
The interesting part of the project is getting all the needed information from several providers via API.
Also since it's kind of legacy project that was done fast and without tests, so we are increasing unit tests coverage, and doing TDD with the new features.
Another problem was MySQL performance, a bad design was making that service consume 80% of CPU. We solved that adding proper indexes and updating some wrong configured fields.
Also, I've been creating NodeJS Lambdas over AWS, that were importing data from third-party APIs to a No-SQL database over DynamoDB.
This project has three services:

• A PHP service that manages all the frontend and the API in charge of creating any content, access control... We migrated that project from PHP 5 to PHP 7, and from Silex 1 to Silex 2... we had fun doing that.
• A NodeJS 4.7 service that does all the searches.
• A new NodeJS 8 service where we are migrating all the searches. TDD with Mocha, Chai and Sinon.

The second one is a new project made from scratch following TDD and DDD. It's fully developed with PHP, using Symphony 3. The unit tests are made over PHPUnit.
It's a website that provides security for personal identification. It's also a product only available in the USA.
In that case, we have 2 services:

• On static content service with Nginx, where we have all the frontend. That frontend is fully HTML and JS, so we don't have PHP mixed there, our API it's fully separated.
• On PHP 7 service with an API secured with OAuth using JWT tokens. The API is RESTful level 2 (see Richardson Maturity Model), but we'll start adding hypermedia, so the idea is to jump to level 3.

The team is following Kanban, and we also use Event Storming for big features or new projects, like we did with the second one.

I was a Backend Developer in a scrum team of 5 devs. We were creating new modules of API Rest based on PHP 7.

The API centralize all data management of the business and sells too.

We used Symfony 2 but only as an application layer. All the business logic was isolated and structured following DDD and Hexagonal Architecture.
Otherwise, we were following CQRS, so we had a read model and write model isolated. And we were using Event Sourcing on majority part of the project.

Security was over OAuth 2.0 using JWT.

After joining them turned out that the company wasn't in good financial health and they closed 3 months after.

Projects:

• Motocard: New ERP to handle website products. Website connection with ERP SqlServer database.
• Inforsa: Develop new API to read data from their data providers from API calls, FTP files... Develop new ERP to handle client and providers liquidations.
• Pans&Company: Website and background processes maintaince.
• Ribs: Website and background processes maintaince.

Migrate old TT2 to new NodoGestion.
Prepare the ERP for new sectors like energy and fishing distributors and factories.

Maintain GestorTT which was a telefony ERP for Telefonica, Vodafone and Orange stores.
I was specifically working on logistics, comisions and liquidations sections.
Migrate old GestorTT to new TT2 based on PHP.

Tailor made websites from scratch and Drupal adaptations. Also, Drupal plugins creation.
I did corporate websites, social networks, backoffices, online shops...

Tailor made websites from scratch and Drupal adaptations. Also, Drupal plugins creation.
I did corporate websites, social networks, backoffices, online shops...
Also, I was doing server administration for web, DNS and mail services over Debian servers.

New computers assembly and maintenance.