Sections

Pipi 7 (2020)

Mike's Notes

A Brief History of Building Pipi 7.

Resources

  • Resource

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

30/05/2025

Pipi 7 (2020)

By: Mike Peters
On a Sandy Beach: 01/03/2021

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

When Pipi 6 was finished, it was already overdue for replacement, given what I had learned from building it.

2020 Starting

The most significant change was the adoption of microservice architecture. Each microservice has a separate database, logic, workflow and web presentation layer. There were 300 microservices and lots of drawings inside 6-sided polygons.


I must have left a big trail of smoke from my Google searches, because Google started calling me every two months. Initially, I ignored them, but they wanted to host Pipi on Google Cloud Platform (GCP).

So, I optimised the internal architecture for cloud hosting on GCP using their platform tools.

A rules engine was built to handle logic. CQRS messaging that included persistent data storage.

The platform's self-documentation utilised ColdFusion.

Influences

2020 Finish

It looked good, and then it was ready for a complete rebuild (not even a refactor). However, the microservices architecture wouldn't scale because of the growing complexity caused by the Covert cell simulator-derived components. Docker wouldn't work, and it would now require a Virtual machine (VM).

Back to the drawing board.

No comments:

Post a Comment