Mike's Notes
Thursday, 09/04/2026 (NZ time) was a very long day. I couldn't make a single mistake, so I turned off the phone and the internet to concentrate from 8am to 9pm, then slept like a log. I was a walking zombie yesterday. I'm glad this will never need to be done again.
This is the successful culmination of months of challenging preparatory work for the new Pipi Core data centre.
Resources
- https://www.blog.ajabbi.com/2026/04/pipi-naming-pattern.html
- https://www.blog.ajabbi.com/2026/04/pipi-core-directory-structure.html
- https://www.blog.ajabbi.com/2025/08/enterprise-plan-directory-structure.html
- https://www.blog.ajabbi.com/2026/04/pipi-autonomous-read-eval-print-loop.html
- https://www.blog.ajabbi.com/2026/04/cfml-64-bit-and-32-bit-datasource.html
- https://www.blog.ajabbi.com/2026/03/cfml-applicationcfc.html
- https://www.blog.ajabbi.com/2026/02/having-data-centre-changes-roadmap.html
- https://www.blog.ajabbi.com/2026/03/nvidia-gtc-keynote-2026.html
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
11/04/2026
Pipi Nest
Mike is the inventor and architect of Pipi and the founder of Ajabbi.
Inside the Pipi Core data centre, the careful migration and reorganisation of hundreds of thousands of Pipi-related files began and were completed yesterday. Each file was placed in only one Pipi Nest, and then the historical Pipi Nests were converted into zip archives.
It is a good solution, but it took a month of trial-and-error data centre experimentation to figure out. It had to be 100% correct to enable rapid, reliable automation, self-managed by Pipi.
It was fascinating to watch the recent Lex Fridman interview with NVIDIA CEO Jensen Huang, who described a large-scale problem-solving process.
Problems to solve
A large number of problems had to be solved in parallel. Each problem affected the others.
- Where to put self-organising Pipi swarms.
- Pipi instances
- Naming
- Self-evolving
- Versioning
- How to use DevOps automation with all of the above.
- The knock-on effects on
- Namespaces
- Backups
- Replication
- Accounts
- Workspaces
- i18n
- Web URLs
- Documentation
- Training
- etc.
- 100% security and privacy
This has caused some changes to the underlying Pipi System Engine (sys) data model, which I will write about tomorrow.
Pipi Nest
The fundamental organising principle is to use a uniquely named directory, now named as a "Pipi Nest".
The unique name is a string combination made of
- Pipi Major Version (integer)
- Pipi Edition (lowercase letter)
- Account Class (lowercase letter)
Data Centre / DevOps
Here are some examples.
- 6pg/
- 9ae/
Backups
Customer backup examples.
- pipi_9ae_ajabbi_data_pg_20260411
- pipi_9ae_ajabbi_pipi_www_learn.ajabbi.com_20260411
Archiving
Here are some examples.
- pipi_6pg_20180219.zip
- pipi_9ae_20241211.zip
Next job
I can start on configuring the files and settings for each Pipi Nest. The necessary code has already been successfully tested. Eventually, this process will be completely automated.
- Application.cfc
- server.xml
- Datasources
- OS environment
- Java
- Application server
- Cloud platform
- REPL
Speed is King
Then, each Pipi will be back in business and can be left running 24x7 in its own nest, thereby increasing DevOps speed by at least 10x. The priority now is to increase Pipi's Data Centre speed by 1000x and keep going. So what previously took a year can be done in an hour. The deadline is June 2026.
Future customers
The increase in speed will also directly benefit all future customers using the SaaS workspace applications. Deployments, configuration, and updates will also get the same 1000x speed increases at no extra cost.
No comments:
Post a Comment