Rodolfo Torrez Email & Phone Number

Rio De Janeiro, Brazil

Winnipeg, Canada Area

Farewell Brasil... hello, Canada! I'm a member of the Payment and Fraud Prevention team, a core team of SkipTheDishes customer's domain. As an SSE, my role is to help the team to think, design, improve, fix, mentor, solve complex problems and do whatever we can to thrive and make our applications better using all techniques and tools we've at our disposal. Some are Java 8, Spark, Docker, Maven, Jenkins, Git, AWS, MySQL, ElasticSearch, RabbitMQ, etc. As a company, we have a considerable challenge - redefining how people get their food and focusing our strengths on "Serving The World’s Greatest Menu. Brilliantly!". It looks like a lot of work to do, so... let's get started!

Rio De Janeiro Area, Brazil

What now?I led the Checkout team - the same team that I started. The Ideais brand no longer exists. We joined the Cart, Payment and Order teams. Some changes happened in the company, making sense for us to do that. And I was entrusted with the responsibility to lead this team (we were four people), responsible for 17 APIs serving the entire e-commerces checkout process (Americanas.com, Submarino, Shoptime and Soubarato). There you can ask: four guys to take care of 17 APIs? How is it possible? It wasn't easy, but with a lot of competence, desire to learn, organization, communication, teamwork, and the right tools were possible. Some are Java 8, SpringBoot 1.5, Tomcat 8, Docker, Gradle, Bamboo, Git, AWS, Datomic, DynamoDB, MongoDB 3.4, Riak, etc.The team still takes care of a "product" that generates ~3.2B - GMV and ~1.1B - Marketplace (see link below) for the company. It may seem scary and intimidating, and any mistake can be disastrous, but that motivates us; it is our fuel to tread the road of continuous improvement."With great powers bring great responsibilities."And tomorrow? What to expect? Always the best.

Rio De Janeiro Area, Brazil

Bye-bye monolith ... hello microservices!In 2013, Ideais was acquired by B2W, and with this, we gained more autonomy to propose and implement improvements in our apps and architectures. After a fateful sales event, in which practically all the applications fell (including ours), we saw that we had to change everything quickly. When we met and decided to redo all of our application and production architecture. We will adopt the architecture of microservices and use cloud computing, no longer manage servers in production, no more Weblogic, applications will only have a well-defined responsibility, will be light, stateless. With the monolith breaking, several APIs appeared and the need for new teams to manage, maintain and evolve them. It was then that the opportunity arose to take on a new team that took care of the APIs responsible for the payment information (called the Payment team).With autonomy, goodwill and capacity, we began to assemble the new APIs, using what we could find the most recent in the market. Some of the technologies that we adopt: REST/APIs, Java 7, SpringBoot, Gradle, Git, Tomcat 7, AWS (Elasticbeanstalk, SQS, SNS, etc), Oracle, Bamboo (CI), MongoDB. The work was hard, but it was gratifying because, at the end of 2014, we succeeded in doing until then, the best Black Friday in the company's history, with 100% uptime.While passionate about coding and learning about new technologies, as a team leader, I needed to develop new interpersonal skills to help my team develop professionally and as people. I believe that this is possible through a channel of open communication, knowing the individual needs of each one and how to keep each one interested and why not, motivated to give their best and be part of something great. This is my big daily basis challenge.

Rio De Janeiro Area, Brazil

With good experience in developing Java applications, I arrived at the Ideais to occupy a senior developer position. I was directed to the team that took care of the application and was responsible for managing the entire B2W Checkout process (americanas.com, submarine, shoptime). It was a Java EE 6 web application, a giant monolith (.ear file), running on WebLogic 10, made in Java 6, JSF 1.2, Hibernate, backed by Oracle database. We suffered enough to keep it working. We had problems deploying and scaling (Weblogic hell!) and some issues keeping the state and user session (JSF hell!). On the other hand, it flowed very well, we used Scrum for this, and the team's maturity was excellent. Planning sprints, review, retrospective, everything was going well. The use of agile methodologies like XP (pair programming, TDD, code review) helped maintain good product quality. As a senior developer, I always helped other team members, especially the juniors, in language learning, technologies, and our methodologies in the development process. But as B2W e-commerces grew, app scalability and availability problems were worsening. We needed to do something to change that.

Rio De Janeiro Area, Brazil

Bye-bye, Delphi... hello, Java! In 2008 C&V went through severe internal problems, and because of that, many of us had the contract terminated. Once again, a friend who worked with me pointed me to a developer position, and that's how I met M4U. The job was for a Java developer, and I had almost no professional experience. Still, I had experience in software development and a lot of desire to learn.They were starting an innovative m-pos project, a 100% mobile recharge phone credits point of sale. And that's where I came in. Two Java applications were entirely server-side and one running inside the sim card (Javacard). The stack of technologies we used for this project was basically: Java 5 (server-side and Javacard), Oracle, JMS 1.0, JBoss 3.1, and EJB 2. Integration with the Servcel was via ISO-8583 communication protocol standard. The asynchronous and well-structured communication enabled us to scale the system well in high-volume scenarios.After this project, other m-payment projects were created, growing to the point where a new company was created to precisely manage the new m-payment projects. Time passed, and the technologies were also evolving, but Java was always present. Some would be Java EE 6, JBoss, JMS 1.1, JSF 1.2, Primefaces, EJB 3, XML/SOAP (web services), Hibernate, and Maven. A few more non-Java: Scrum, JIRA, SVN, Jenkins (formerly Hudson). All applications ran on Ubuntu Linux servers. Our applications had scalability and availability as core requirements, wherein in high volume scenarios, it was necessary to attend approximately 1MM/rpm. To reach this level, our production architecture was assembled with multi-instances of the app behind a load balancer (BigIP / haproxy), failover instances and mirrored and optimized database.

Rio De Janeiro Area, Brazil

The year was 2006, and I wanted to marry my fiancee (now my wife) and needed to make more money. I called a friend who told me about a developer position. I applied for the job and passed. The development area was huge(~ 120 people) distributed across several teams. The systems architecture was client-server, where the technology stack was Delphi 5 + SQL Server. As a medium-sized retailer, the systems were for internal support or support for the physical stores (e-commerce was beginning here in Brazil). But two were the differentials in the type of development: 1- heavy programming within the database (optimized queries, store procedures, T-SQL); 2- batch processes programming. It was exciting to learn the SQL Server internals - creating/managing indexes, organizing the data into memory pages, reading the query execution plan, etc how to program in T-SQL (store proc, code block, temp tables, etc).At this time, I had my first contact with a version control system (VCS), and I remember how this changed my view on codebase organization. Since the architectures were the same among the applications, I participated in a committee whose first version reduced the average development time of medium-sized applications from 2 weeks to approximately four days. The committee also started to learn about agile methodologies (XP, Scrum), clean code and how we could implement this in our daily work. During this period, I worked on the teams responsible for developing the application that managed all active/inactive/schedules that would go to the stores and the application responsible for SKUs pricing. The pricing process consisted of generating text files in the specific format of each SKU sold in each store. In the end, these files were transmitted to stores via SFTP. It was great learning to work with larger systems that needed to scale and serve multi-user.

Rio De Janeiro Area, Brazil

After the SPB went into production, everything went well, but I felt I needed a new challenge. A friend pointed me to a developer position, and that's how I met ZAP. A small company (~10 employees) was setting up a team to develop its newest financial product - ZAP Open Market. It was a system that controlled transactions between financial institutions (buying and selling bonds).I was the only developer on a small team (3 people). The architecture was also client-server almost - after all, it was 2002 - but it had a difference that the client part was split into 2-tier (client + application server). Our architecture was in 3-tier (client, application server and database). The client was the view (forms) controlling the visual presentation. The server application was running on a separate machine. Finally, the database (any similar to MVC and pure coincidence ;) even because I didn't know what MVC was at that time. Our technology stack was Delphi 5 (again, do not judge me) for the presentation and application server and Oracle for the database. The 3-tier were running on the 32-bit Windows platform, and we used COM+ as the communication protocol between the presentation and the application server.It was challenging for a beginner like me to program in 3-tier architecture and work with COM+. At the end of 2002, we already had two clients, and by the middle of 2006, we had approximately 20 clients when I left. We still had time to develop a new product (using the same 3-tier architecture) called ZAP Swap - to control derivative contracts. While I was working on these projects, I realized that the quality of my work was better when I understood the business rules. I learned how important it is for a developer to have a holistic view of the business domain and not be just a task performer. I also made great friends that I take until today, which taught me a lot about being a professional within the work environment.

Rio De Janeiro Area, Brazil

After a short two-month internship, my first job as a programmer (after a brief two-month internship) was in a startup building a new product called Sistema de Pagamentos Brasileiro (SPB - to know more http://www.bcb.gov.br/htms/novaPaginaSPB/VisaoGeralDoSPB.asp). I was keen to do something different, and it would have a significant impact; after all, the SPB would be a system of national-wide implications and should be used by all banks and brokers in Brazil. The year was 2001, and what I can say - desktop applications reigned!The architecture was client-server with the client part made in Delphi 5 - please do not judge me ;) - and the database being Oracle, SQL Server or DB2. I helped create an abstraction application internal layer for the database to achieve this flexibility. The connection settings were external to the application, and all queries and database statements (DDL, DML, etc) used ANSI-SQL to maintain compatibility and keep only one codebase.We used an IBM MOM solution called IBM MQ (MQ Series - http://www-03.ibm.com/software/products/en/ibm-mq) for communication between financial institutions running on Windows 32-bit platform. The messages were in XML with strict schema (using DTD) developed by the Central Bank of Brazil, coded using asymmetric cryptography (via certificates) and encoded in EBCDIC. It was a real challenge for a newcomer like me first to understand what all these letters were and how they fit together. Still, it was incredibly enriching and enjoyable to see when after several months of testing, the first customer went into production in January 2002.