AWS, Spring Boot based microservices on an event based architecture (Apache Kafka) for Mercedes Benz?s electrical vehicle charging station platform.

• Backend development of microservices
• Helping in designing the event based architecture
• Code reviews, etc.

• Development and deployment of Spring-Boot based Microservices and Batch Jobs into the Google Cloud for Germany?s equivalent of ?Best Buy?.
  
• Design and workflow creation of data consolidation of several independent systems into a centralized system.
• Development of internal web-based administrative tools based on Phoenix LiveView

Migration of a JBoss monolithic code base to a microservices based architecture.

• Refactoring of code base into micro service
• Docker containerization
• Jenkins Pipelines
• Integration Tests (Postman)

Migration of ECC/AMI based Spring-Boot Microservices to Java 11 and Docker containers

• Source Code modification to use Java 11, AWS SecretsManager
• Docker Containerization
• CodePipeline Runs and Debugging
• Postman Test Creation per individual app

Migration from an On-Premise environment to AWS for future scaling requirements. Parts of the application were redeployed as Spring-Boot based microservices in Elastic Beanstalk, with RDS databases. 

• Migration of databases
• Development and Deployment of Spring-Boot Microservices
• Cloud Administration
• DNS Setup
• VPN Access
• SQS/SNS Setup / Administration
• Java
• Cloud
• AWS

The application was written in Java 8 and compromised of 7 Spring Boot based microservices hosted on AWS. Development made use of Docker containers. Initially all microservices were deployed as Elastic Beanstalk instances but then were consolidated and redeployed on AWS docker hosts. The purpose of the application was to provide the infrastructure for a smart charging feature for owners of BMW?s electrical vehicles in California. 

• git code migration from single repo to individual project repo
• internal maven repo set up
• CI/CD pipeline creation (bamboo)
• migrated large chunks of business logic from code to SQL
• migrated data and code from mongo to Postgres
• introduced programing against abstract interfaces so that implementations could be developed independently from their usage
• Java
• Cloud
• AWS

The project involved working on Universal Studio?s Data Analytics department, in particular the ingestion of large amounts of data using Apache Nifi. Apache Nifi/ Horton Works is a Java based ETL software which we extended and adjusted through supplementing and altering the Java code base. 

• Porting of Nifi Flows to a newer Version of the Hortonworks Platform
• Introduced XML/XSLT to represent database schemas and column type conversion between import from source systems, external (temp) tables and managed persistent tables. The above approach allows for the generation of HiveQL statements and for the creation of temp (external) tables in which columns are untyped (strings basically) and managed tables which have more refined types via XSLT. This also includes the automatic generation of select ? insert from statements in HiveQL in which the values are converted accordingly from a single source of truth. The approach naturally scales to any number of tables and was adapted by the team.
• Discovered an already existing processor for incremental import. The previous approach used data dictionaries and a complicated logic.

The application, which is written in Java 8, serves as a unified facade to several cloud providers such as AWS, Azure and VMware. It allows the client to provision, control and monitor virtual machines from several cloud providers from a single access point. The application itself was hosted on AWS. 

• Implemented middle tier logic for a unified Cloud Management System as Microservices
• Configured, administered and bridged supporting external software systems
• Assisted and advised the team architect with design decisions and build cluster prototypes (in OSGi)
• Oversaw and initiated effort to split repo from single repo into multiple repos while preserving histories
• Introduced architecture which favored discretely defined API packages with accompanying default implementations.
• Introduced semantic versioning.
• Mentored junior and senior team members in the benefits and usage of the above approach.
• Introduced java client packages (APIs and implementation) for each existing micro service that hide and abstract from the REST mechanism (Of course the implementation still sees it).
• Added a default and flexible persistence interface which included validation, encryption and decryption as pluggable components (functions basically) instead of using OO inheritance.
• Setup and configured Jenkins for automated builds and versioning (in a docker container) to support the multiple API packages style.

The application was written in Java 8 and consisted of several Spring Boot based microservices. It allowed small business customers, to ?sell? their invoices on the platform and receive immediate payment instead of having to wait 30 days for the invoices to be paid. The application interfaced with 3rd party systems, such as a partner bank?s computers. 

• Implement and design Microservices in Spring Boot for a financial services platform
• Specify technical and functional requirements
• Negotiate technical details with partner companies
• Java
• AWS
• Cloud

The application was written in Java and served to support the client’s field agents, a financial services provider. 

• Senior technical contributor to two concurrent JEE based projects
• Served as an interface/ liaison between DevOps/ Testing teams.
• Worked in a self-organizing/ pre-emptive manner, provided technical guidance and mentoring to junior team members

The application was written in Java using the Spring Framework and deployed in Tomcat containers. In particular we made strong use of Spring Batch for data imports. It served as an internal tool within BASF for billing purposes. 

• Senior technical contributor in a team of 9
• Introduced alternative approaches/technologies to an outdated team skill set
• chaired SCRUM meetings occasionally

The project’s aim was to port several, internally developed, mostly MS-Access based applications to a web-based, unified tool box. We have rewritten these applications in Java and hosted them on the company’s internal network. 

• Architect/ Technical Lead on several Desktop to Web migration projects
• documentation of technical requirements
• responsible planner/ coordinator during lifecycle

• coordinated a team of mostly non Java developers
• designed application architecture
• designed and implemented code foundation

The project’s aim was to port several, internally developed, mostly MS-Access based applications to a web-based, unified tool box. We have rewritten these applications in Java and hosted them on the company’s internal network. 

• Architect/ Technical Lead on several Desktop to Web migration projects
• documentation of technical requirements
• responsible planner/ coordinator during lifecycle

The project’s aim was to add new features and customizations to a Java/ OSGi based payment system. 

• worked in a multinational environment
• implemented client specific business logic in addon modules
• contributed domain specific knowledge due to financial background

• Architect/ Technical Lead on several Desktop to Web migration projects
• documentation of technical requirements
• responsible planner/ coordinator during lifecycle

The project’s purpose was to develop an ETL tool in java/ Spring Boot. This tool was used primarily to extract data from very large XML files and load them into an Oracle database. 

• design of a streaming architecture for ETL of large XML files into an Oracle DB
• knowledge transfer and Java training to permanent staff
• preparation of presentations for staff training

The client, a medium size advertising agency, need a CMS for their website. I have developed a user friendly CMS in Java. 

• Designed and implemented a Java based CMS
• held regular meetings with staff members
• trained staff in CMS use