Please enable JavaScript.
Coggle requires JavaScript to display documents.
CCI API Patterns project - Coggle Diagram
CCI API Patterns project
What we did well
-
Communication
We didn't shy away from delivering bad news. i.e. When changes that were expected to fix/address and issue didn't work as intended
-
Flexible
We were flexible when it came to adapting/Implementing changes requested by the client. i.e. Swap out the ubuntu for Red Hat on the Kong EC2 instances because the security team preferred that OS to standardize patching and other related routines
When Alex left, we were able to pivot and ramp-up new CCI dev on the project in a short space of time
Documentation & Handover
We hosted a number of workshops to ensure that the new devs could get their hands dirty and comprehend easily
-
What we didn't do well
-
Performance testing
Spent too much time on proving that the solution/architecture would be able to match the expected performance expectation
Part of this was due to Alex's gloom and doom messaging around his testing. I believe could have assisted him more in his testing venture to settle on the results
The way we allowed the client to go about performance testing left a lit of room for error and misinterpretation of the results
What we learned
API Gateways
We looked into a plethora of API gateway tools and got a pretty solid understanding of what their strengths and weaknesses are
-
Kong
Learned the ins and outs as we were able to install, setup/configure and run it successfully
Snowflake
We were able to build on our existing knowledge and experience with snowflake and level that up, ensuring that we were able to hit the performance milestones
Terraform
-
We were able to ramp up quickly and figure out how to best structure and manage the creation of AWS resources
AWS
-
Special Call out to Javier: He never worked with AWS before in this capacity and was able to ramp-up, execute and deliver
Call outs
Relationship
We were able to build on the existing relationship from the Eurostacker project and establish a better working relationship with the client.
-
What started off as a potential hostile relationship with Alex, eventually became a respectable environment. This is a result of Headspring creating an fostering a non threatening workspace that encouraged collaboration