Java Architect with MiddlewareEDI - 100 REMOTE

We are looking for a Java Architect for 3 hours a day for 8 weeks for a senior 10 year consultant

The tentative start date of the project is November 11^th 2024. Through Jan 10^th given the holidays in between.

The engagement is more of prediscovery to win the deal to figure out how to develop and deploy the existing middleware and EDI interfaces written in Java with about 400500 different classes in a brownfield manner in a new environment. With SAP backend and some COTS systems we are to assume that we will have the COTS ecosystem available in the new environment for the brownfield deployment.

The tools and technologies are play are

1

Peas

Web development and execution platform

Development

Framework

2

Aluminum

Redmine allinone

Project management

Tool

3

Jenkins

CI/CD tool (Continuous Integration/Continuous Delivery)

Development/Operation

Tool

4

Git

Source code repository

Development/Operation

Tool

5

Maven

Module configuration management

Development/Operation

Tool

6

Eclipse

Integrated development environment (IDE)

Development

Tool

7

NetBeans

Integrated development environment (IDE)

Development

Tool

8

Asteria

Batch/service development environment

Design/Development

System

9

Webtom

Migration management

Development/Operation

System

10

Java

Language

Development

Middleware

11

Tomcat

Servlet container

Development/Operation

Middleware

In addition here s what we know

Middleware facilitates communication between applications databases and users. In this architecture middleware services play a critical role in ensuring communication between the frontend users and backend systems.

Nginx Load Balancer (DMZ and TRUST Zones):

Nginx (dual node) is positioned in both the DMZ and TRUST zones. It acts as the primary middleware component for load balancing handling incoming requests from external users and routing them to appropriate application servers.

It ensures efficient traffic management and distributes the load to PABC application servers (both in the DMZ and TRUST zones).

Intranet Load Balancing Server:

This server located in the TRUST zone provides internal load balancing. It manages traffic within the system and ensures high availability and distribution of requests to the internal application servers and databases.

ASTERIA Server (for API Integration):

The ASTERIA server (labeled as Midget) likely serves as middleware for integrating external APIs such as those used by SAP. It helps connect external systems with internal applications in the infrastructure ensuring smooth API communication.

Redis Server:

The Redis Server is used for caching and is a common middleware component for fast data retrieval. It reduces the load on the database by caching frequently requested data acting as a keyvalue store for application data and ensuring high performance.

Tableau Server:

Tableau is a middleware for business intelligence and analytics. It allows for the visualization and analysis of data within the architecture. It acts as an interface between databases and endusers presenting data meaningfully for business decisionmaking.

Oracle Database Servers:

Oracle Unified DB Oracle Talent DB and the Oracle Database Servers manage data storage and retrieval. They provide the backend database functionality and middleware components like API servers interact with these databases to store and retrieve businesscritical information.

Message Broker Components: Kafka is being used as Message broker

XXLJob Server:

This server might handle scheduling and job execution as an intermediary between different services. Though it is not a traditional message broker like Kafka or RabbitMQ it could manage job queues or scheduled tasks facilitating asynchronous communication between different system components.

Application Servers:

The application servers manage and process requests from users and external systems. These servers interact with middleware components (e.g. load balancers and databases) and likely use internal messaging systems to handle API requests and responses.

Other Key Components:

Base Servers (DMZ and TRUST):

These servers (labeled 1 2 in DMZ and 3 4 in TRUST) are crucial for the operation of the application. They serve as the foundational layer where applications and services are deployed managing incoming and outgoing traffic.

PG Database Server:

The PostgreSQL database server cluster stores the business data and handles requests from application servers. Middleware components like the load balancer and API servers likely interact with these databases to store and retrieve application data.

Lavoro Server:

It is unclear exactly what "Lavoro Server" handles but it could be related to handling specific business processes or workflows potentially acting as an intermediary or middleware for specialized tasks within the infrastructure.

We need to come up with relevant questions to ask see if we can leverage pseudocode generators to generate an algorithm/pseudocode from exiting source code to expedite the development after the win and finish brownfield deployment in the new environment no more than six months later.

The current deliverables will include the necessary plan documentation and pseudo code or if provided access to existing source code and documentation to be able to complete the deployment successfully.

Requirements