Inspiration
The motivation for this project is to create something to process rejected messages that need to be handled automatically, reducing manual effort in communication, backtracking and debugging.
What it does
The project polls rejected messages everyday from a database and would process them according to the preference of different business units.
How I built it
The project consists of several databases tables, a SOA application using Java, SQL, to fetch and filter through rejected traffic from web services. The logic and design of the application allows for future integration and development for more features.
Challenges I ran into
One of the biggest challenge for me is that I was new to Java at the time. And that I did not know much about web services, and there was a lot of learning throughout the process of building the application. But overall not concerning the tech, another aspect that was challenging was testing, and having a grasp on the format of the messages. This leads to tradeoffs between querying more messages with more false positives, or querying less messages with missing true positives.
Accomplishments that I'm proud of
I am proud that the project was completed and serves as a good starting point to automate the process with rejected messages on web services in the company. There are a lot of features that can be added to the project, and the potential is endless.
What I learned
I learned that trying to work with but not knowing the technology might be overwhelming at first, but I should be brave to tackle the learning curve because everything will be more intuitive with practice, just like how I learned and improve throughout this project.
What's next for Rejected message handler
The web service has been deployed, but the team has flexibility to expand on it, such as : types of messages, new methods to react to these messages...etc.
Log in or sign up for Devpost to join the conversation.