Victor Rusu Email & Phone Number

Key responsibilities: architecture, implementation strategy, execution, identification and solving technical impediments.Team orientation: recruitment, mentoring, training. Architectural paradigms: SOA/Microservices, Event Driven Architecture.Architectural patters: Hexagonal/Ports and Adapters, CQRS.Application integration: Rest, messaging.Tactical design: SOLID, Design patterns, Actor Model.Toolstack: Java, Python, Terraform, AWS, TDD/BDD, git.

New York, New York, Us

Being a lead engineer I was responsible for: product roadmap, definition of implementation strategy, architecture, execution, identification and solving technical impediments. While working in an Agile environment, I enjoyed writing code in Python with my teammates, conducted code reviews following Solid, Kiss principles. During lunch and learn session I gave talks on following topics:-Ports and adapters + servicehost application structuring;-Ports and adapters - the testing part; -Strategies for building features while surrounded by legacy systems;-Effective design with Domain driven design;-Strategical patterns of Domain driven design. We used right tools for the right job. Microservices/Soa as architectural style by applying effective design facilitated correct system assessment from perspective of business value and complexity.Tool stack: Python, Flask, TDD, Aws Lambda, RabbitMq, Kinesis, SQS, DynamoDb, S3, Node.js, C#, ASP.Net Web API, Liquibase, MySql, Fluentd, Docker, Unix, Postman, Swagger

New York, Ny, Us

Schedule changesThe Schedule Change Management System is one of the core elements in handling post-booking itinerary changes. One of the biggest challenges was complexity that we had to deal with, finally achieving:- human intervention only in exceptional cases;- no human processing mistakes;- schedule change processing in matter of seconds since it's published; Derived solution is a set of reusable behavior based components implemented as services. The benefit of this approach is that independent solution parts could be scaled out (some of them are used in other business process' implementations) as needed. Communication between components is request/reply or messaging - depending on temporal coupling. Applying OO Principles and following TDD the solution is well documented - requirements are implemented as scenarios, flexible, transparent. Tools: C#.Net 4, Asp.Net MVC 3, Azure Servicebus, Azure Table Storage, WCF, Ninject, Castle Windsor, MongoDB, Sql, Moq, MSTest, NLog

Secaucus, Nj, Us

Order management system.The goal we had, was to build a reliable, high available and scalable system.As a team member I:- was involved in identification of bounded contexts and contexts' maps; - implemented orchestration of order processing based on enterprise integration patterns;- elaborated functional and behavioral model of Sales business component.Achieving the goal, business feels benefits of:- reliable order placing(no more lost orders).- fast order processing.- audit log.- fast reads.EnvironmentMethodology - agile, scrum techniqueTools: C#.Net 4, Asp.Net MVC 3, NserviceBus, WCF, MSMQ, Ninject, Entity Framework, RavenDB, Sql, Moq, Nunit.

Bristol, England, Gb

Project AdvanceEnterprise application for the administration, documentation, tracking, and reporting of training programs.Responsibilities:- implement user stories;- solution research;- learn/follow TDD/DDD/CI practices;- design following SOLID principles;- develop and structure code in patterns and testing-code following xUnit patterns.Tool stack: .net 3.5, asp.net MVC, Windsor, NUnit, Moq, CI, TeamCity, MsSql2008, FluentNHibernate, Elmah, jQuery, IIS, SVN ,ReSharper