Return to site

Where Are All The Infrastructure Design Systems?

It's a Miracle Anything Works At All ...

I love designing systems. I hate not having a system to help me design them.

How do you architect and design a new system ? Probably with Excel and Visio. That’s great for overall architecture, layers, pieces and parts, but not very good for the real details, configurations, and change management, let alone any ability to confirm the system actually conforms to the design. Nor very helpful in actually building it.

The world should have a good large-scale infrastructure and service Design System.

There are a few “Cloud” Management Systems that do “Design” by drawing out a cloud VPC, VMs, and other cloud features, including choosing the various parameters for these things. But they have exactly zero for the services running on top of them, such as web servers, app servers, databases, caches, and much more. Not to mention no way to manage all the versions, changes, and deep configurations of all these things. Nor any reverse engineering, rule engines, best practices, or other tools you need.

A good design system should do all of these things, at every level, from the physical servers and common clouds layer, to all the services like Nginx, MySQL, CouchDB, etc. to clusters of these things. Across all common versions and editions, which is about 10 for MySQL/Percona/MariaDB, six for PHP, and five for Java, all with their own design options, rules, and best practices.

Design Systems should of course have templates, but also cross-check things so you don’t set MySQL for 16GB of Innodb Buffer on an 8GB AWS VM. And enforce security and other rules so you can run Redis as root or open firewalls to the world.

A very good Design System can version the systems and have Change Control, so it can issue change sets on existing servers, allowing engineers to make updates in a managed, controlled, and audited way. This is not easy on most systems and clouds as there are myriad rules for changes, restarts, rebuilds, and cloud-specific challenges to each. It’s very easy to break things this way.

And a great Design system can reverse engineer any existing system on any common cloud or physical hardware, to build a virtual model to be modified to make changes, clone, or rebuild a system. This enables true logical migrations to/from and between clouds, too.

Finally, any useful Design System needs to export the design to, or integrate with, a build system such as Cloud Formation, Ansible, Terraform, Cloudify, etc. to provision, build, configure, and change these complex systems over time.

Where do we all get a system like this ?

We couldn’t find one, so we built it, now in its fifth generation, and now we are releasing it as part of our OpsStack Cloud Operations Platform.

OpsStack and the Design System can and will do all of the above and more, covering 500+ design points for all common versions of everything, for common clouds, technologies and services, and more plus templates, rules, audits, and integrations. With a long roadmap of future features, too.

This is the Design System of the future, for Operations Engineers working on real systems of any size, any type, anywhere.

Contact us today for more information about our Design System and its parent Operations Platform, OpsStack

All Posts

Almost done…

We just sent you an email. Please click the link in the email to confirm your subscription!