This was a project with a story to it, so before plunging into the development processes we scanned it for the bottlenecks. The major issue was the system complexity. ETL projects aren’t the most demanding in terms of technical execution, as this is a mere process of transferring data from one database into another. Yet, mastering ETL tools can be a challenge, as it was the case for the previous vendor who tried to move the whole ETL process to the cloud and got stuck in between. The solution lacked clarity and clear structure.The system was a mix of the monolith and microservice approach, with several stand-alone services each having their own code base and running on a separate server but sharing one database.
For now, our team has stabilized the system operation by unifying its logic where it was a reasonable choice.
Knowledge transfer process was hampered, too, as the previous vendor understandably wasn’t exceptionally willing to help after getting a cold shoulder from the client. The documentation was inadequate to the team’s needs.
The project data is complex, denormalized and poorly structured. The Symfa team gets their portion of the data from the source which is extremely denormalized for a different kind of reports. To get those denormalized data fit for our purposes required much self-studying and commitment from our team, which our guys showed before and continue to do so each day of the ongoing project.
Our team will get back to you promptly to discuss the next steps