Márcio Winicius

- Define a software system structure, including its components, how they interact, and how the system works as a whole. - Choose the programming languages, frameworks, tools, databases, and cloud services that best suit the project, taking into account factors such as performance, security, and scalability. - Define standards for code quality, system performance, and security, and monitor compliance with these standards. - Work closely with customers, product owners, software engineers, and other stakeholders to understand requirements, translate them into technical solutions, and ensure that the system meets business needs. - Evaluate and select the most appropriate technologies and frameworks for the project, considering business constraints and requirements. - Provide guidance and technical support to developers, helping them implement the system architecture and solve technical problems. - Create clear and concise documentation that describes the system architecture, components, their interactions, and design decisions. - identify and assess the risks involved in the project, such as technical, security and business risks, and develop mitigation plans. - Continuously seek ways to improve the system architecture, such as improving performance, security or scalability.

Developing microservices architecture with PHP and GoLang with conversation between them via GRPC and HTTPS. Technologies used: - Docker/Docker-compose: we use it to provide a local development environment similar to what we use in production and/or sandbox. - GoLang / Gin: we use it to do some projects that need a high load of requests and a high performance. It's a good language to work with that combines very well or low/high level programming. - PHP / Phalcon / Laravel / Slim: we use it in many projects within some teams that are already made in this language and framework. - GR: some microservices that we deal with GoLang, we chose to improve their collaboration with GRPC, as it traffics binary data and is an HTTP2 protocol. - HTML/CSS/JavaScript: technologies we use to develop application front-ends. - MySQL / PostgreSQL: Database related is used in many projects. mainly in B2B and ADM projects. - Database of data, we use not to be possible a large number of information related to very good storage: and we also use applications to save the information. - Messaging / PubSub: we use it for asynchronous conversation of microservices. - Schedules: we use it to run some project routines. - Queues: we have some microservices that deal with high data input, so we end up processing in queues. - Redial or redial a database in many memories: how we use the application cache. Microservices: We have a lot of projects that have a microservices architecture, just a few much older projects that we don't use. - AngularJS: front framework of some applications. - ReactJS: front framework of some applications. - Git / Bitbucket: code versioner that we use - GCP: Cloud that we use. And I'm also a tech lead at the time of innovation.

Fullstack developer for the team that works on the management project of all the data that the company captures. Working with technologies/frameworks: - PHP: main programming language used in the various projects of the team. - MySQL: relational database used in all team projects. - Datastore: non-relational database used by all projects to save application and request logs. - Messaging / PubSub: messaging service that some projects use for conversations between one project and another was done asynchronously with PubSub. - Queues: we had some spreadsheet imports that we had to do, so we put the processing of these spreadsheets too large to process in a queue. - Redis: we use it as an in-memory database to save applications cache (database queries and other things). - Schedules: some applications have routines that need to be activated every time. - Slim 4 Framework: some projects were made with microservices architecture using this PHP framework. - Phalcon Framework: older projects use this PHP framework, it is very fast processing requests. - AngularJS 1.5: the data administration project uses this front-end framework for data presentation (visual part of the project). - Docker / Docker compose: used in all projects to provide a development environment similar to the production and/or sandbox environment. - Git / bitbucket: used for code versioning and for triggering pipeline deployments. - GCP: cloud that we use to host all the team's projects. - Sometimes I'm part of the service as a tech lead, doing some Code Reviews and going to technical meetings.

Project manager, managing a team of 11 people (and growing), separating them into multiple teams for various company projects. I also serve as a reference to solve certain problems because I have extensive experience with software development. I also developed some more complex features of some projects. The main activities as a manager were: - planning the execution of a project dividing its stages into achievable phases; - define the scope of the project, mapping all the necessary work, all its stages and phases; - assemble the project schedule; - pass the project on to your team; - allocate employees in each function for the execution of a project; - distribute tasks; - define deadlines for the execution of each task, stage and phase of the project; - monitor the execution of each phase; - perform daily, weekly and monthly monitoring of projects; - ensure the delivery of the project on time and with the quality standard met.

Creation and maintenance of Restfull API's with PHP using Laravel framework. Using docker for the development environment. Working with technologies/frameworks: - PHP: main programming language used for microservices. - MySQL: some microservices used this relational database to store information. - Laravel: main PHP framework used in microservices. It is a framework widely used by the PHP community, it has a lot of resources and very good documentation. - NodeJS: some microservices use NodeJS as a programming language, as there were some features that helped us solve some problems, for example web socket is very easy to implement with NodeJS. - Express: together with NodeJS we use this very robust framework and widely used by the NodeJS community. - Firebase: some microservices needed a realtime database, especially microservices made in NodeJS. That's why we chose to use this realtime database. - Queues: we had some features that processed a high volume of data in NodeJS. So we chose to use processing queues to improve the user experience without crashing the requests call. - Redis: we use it to write some cache to this in-memory database. - VueJS: all projects that had a front-end we did in VueJS. It is very simple and we were able to make Single Page Applications (SPA) with it very smoothly. - Docker / Docker compose: used to provide a local development environment similar to the production environment. - Git / GitLab: used for storing and versioning project codes. It is worth mentioning that here at DataPage we did not have any CI/CD process. - AWS: the cloud we use to host the projects. - Microservices: architecture used in all new projects. - HTTP protocol - Had technical meetings with managers

Creation and maintenance of Restfull API's with PHP using Laravel framework. Docker usage for the development environment. Working with technologies/frameworks: - PHP - MySQL - Laravel - NodeJS - Express - Firebase - Python - Queues - Redis - VueJS - Docker / Docker Compose - Git / GitLab - AWS - Microservices - HTTP protocol - I held technical meetings with managers

Creation and maintenance of monolith systems. Technologies used: - PHP - Laravel - MySQL - JQuery - HTML/CSS/JS - Bootstrap - XAMPP - REST API

Creation and maintenance of REST API's using Laravel PHP Framework. Main technologies involved: - PHP - MySQL - Laravel - Redis - Queues - Docker/Docker-compose - AWS

WEB developer, using tools such as: 1- HTML/CSS3/JavaScript. 2-PHP/MySQL 3-Framework Laravel 4- MVC software architecture 5-CRUD 6-Preventive and corrective maintenance on Linux servers.

Suporte ao usuário em geral. Suporte em computadores.

Users support in general. Computers support.

Computer engineering - Federal University of Goiás.