Project Description: Platform that delivers technology solutions that help marketers gain intelligence from events. It aggregates event activity from multiple sources, analyzes the insights, scores each attendee by topic and pushes that intelligence into client CRM/Lead management systems - in real-time. The system enables sales team to learn more about their customers and shorten their sales cycle. It also helps marketers become more effective with messaging and event organizers the ability to justify the importance of events. Responsibilities and Objectives: Internationalization (i18n) of the whole application, extensive use of Sprint’s functionalities, creation of a Spring based interceptor, creation of tables and entities needed for these new functionalities, added new RESTful services as requested, modified the application’s UI to match with the new i18n features. Modified mailing system module so that it matches with the different languages and latest functionalities. Technologies: Java, Spring, plain JavaScript, jQuery, AJAX, HTML, CSS, XML, ElasticSearch, MySQL, Restful, SOAP, Maven, extensive use of Java libraries, Hibernate.

Project Description: The application consist of the management of different accounts a user has inside the company. A regular user unfortunately had at least to deal with eight different applications in order to do their job. Having each application it's own account (that is user and password) with no possibility of having a SSO (Single Sign On) mechanism. Many times the users locked themselves (one or more accounts) and needed to got their passwords reset, this function could only be approved and processed by a small group of system admins, making the password and creation of new accounts for a particular user really slow (taking, sometimes, days). This application connected to each underlying system and could: Reset the desired account password for the selected underlying app, Create all accounts a brand new employee needs. The main architecture consisted on an abstract "connector" where a connector is a class responsible to connect and interact with the desired app. Each connector implementation had the logic to establish a connection to the app and make the reset or create request, and adding new connectors where as easy as adding a new entry in a db table. Since the underlying apps were old and decentralized, a connector could take more than 5 min to finish a password reset, so it was necessary to have each connector to run concurrently, so the architecture was created with multi-threading environment in head. The resulting app end up with a user password reset for all of their accounts (eight by the time I left) in 7 min, before the app it could be more than a day. Responsibilities and Objectives: In charge of the development of the entire application architecture, the most challenging task was the multi-threading environment, and the development of two connectors that interacted with really old systems such as TN32 systems where I used a free lib based on scraping mechanism. Also had two more developers, to whom I assigned new task to develop. Technologies: Java, MySQL, Hibernate, Spring MVC and Spring app context, JUnit, Maven, HTML/CSS, Taconite, Extended Regex, Tomcat, SVN, AJAX, JSON, Scraping lib for TN32.