https://github.com/samuelmarks/brand-concepts
Brand concepts for new websites, apps, and presentations
https://github.com/samuelmarks/brand-concepts
Last synced: over 1 year ago
JSON representation
Brand concepts for new websites, apps, and presentations
- Host: GitHub
- URL: https://github.com/samuelmarks/brand-concepts
- Owner: SamuelMarks
- Created: 2019-07-06T12:44:44.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2019-11-04T00:33:16.000Z (over 6 years ago)
- Last Synced: 2025-01-28T04:32:02.506Z (over 1 year ago)
- Homepage:
- Size: 9.77 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
brand-concepts
==============
[Offscale.io](https://offscale.io) / [Sydney Scientific Pty Ltd](https://scientific.sydney)—and possibly Sydney Scientific Foundation Ltd—is seeking new concepts for websites, apps, and presentations. Essentially, the goal is giving these brands a recognisable and distinct identity, which clearly and concisely explains: the problems solved; how its solved; and what makes our solution superior.
## Slogans/subtitles
May prove useful, may not, all original:
- The IT infrastructure space is ripe for change. Docker, Kubernetes and friends have taken over the space, as have AWS, Google, and Azure.
- Bring it to 1 laptop. Enable deployment from 1 node to 10,000. Any public or private cloud.
- Build backend & apps, from 1 dev to many teams.
- "Because big companies don't look at small problems"
- "We build what you promised"
## License
All technology created is 100% [Open-source](https://en.wikipedia.org/wiki/Open-source_software). Under ([MIT](https://opensource.org/licenses/MIT) OR [Apache-2.0](https://opensource.org/licenses/Apache-2.0)) multi-license. No patents.
Justifications include—but are not limited to—increased:
- **security**; interoperability (e.g.: OS, programming-language, protocol);
- **extensibility**;
- **community**: potential;
- **standardisation**;
- **onboarding speed**: no signing required;
- **maintenance**: 1-off delivery for one client could mean long-term free upgrades, if the project is then used by other clients/companies/individuals;
- **general quality**: especially with automated metrics, that can be advertised & integrated with Github/Gitlab;
- **development speed**: can rely on libraries produced by others—as well as by us—to produce solutions faster;
- **attractiveness**: engineers like the idea for various reasons, including above, building their portfolio, and freedom to share ideas openly & publicly.
---
## Principles
Scalable from 1 node to 10,000. Build low-level, functional, structures.
### Performance
With the exception of frontends (e.g.: ¾ of [CDD](#compiler-driven-development-cdd))—and our [multicloud](https://en.wikipedia.org/wiki/Multicloud) ([Go](https://golang.org))—everything is built with [Rust](https://www.rust-lang.org). Which has serious performance advantages—beating [C++](https://en.wikipedia.org/wiki/C%2B%2B) in some benchmarks—while also being safer.
### Scaling on the low end
Other [Mesos](https://mesos.apache.org/)-based solutions don't come close to 1 node usability. Really 5 minimum, 11 prefered minimum.
A key differentiator is support on a single node—e.g.: a developer's laptop—all the way up to a clustered deployment (3 nodes), to serious scale (10,000 maximum).
---
## Products
### [CI/CD](https://en.wikipedia.org/wiki/CI/CD) pipelines
[CI](https://en.wikipedia.org/wiki/Continuous_integration)/[CD](https://en.wikipedia.org/wiki/Continuous_deployment) pipelines allow developers to go from code to production deployments, by automating testing, packaging, binding (ports; DNS), and audience-specific feature releases ([canary](https://martinfowler.com/bliki/CanaryRelease.html)).
#### [Dotfile](https://en.wikipedia.org/wiki/Dotfile) style
*Examples: [Travis CI](https://travis-ci.com); [Appveyor](https://www.appveyor.com); [Gitlab CI](https://docs.gitlab.com/ee/ci); [Azure Pipelines](https://azure.microsoft.com/en-au/services/devops/pipelines); [Dockerfile](https://docs.docker.com/engine/reference/builder); & other competitors*.
Take any CI/CD config format as input, produce any as output.
Have own format also, and a static binary that can run on this format.
So now you can self-host your own [CircleCI](https://circleci.com) competitor.
#### [Mesosphere](https://mesosphere.com) style
[Datacentre operating systems](https://dcos.io). Again, like all Mesos-based technologies, it's for medium to large scale deployments only. With Offscale.io's contributions, it can now work on a single node.
### Compiler Driven Development (CDD)
An alternative to [Xamarin (C#) from Microsoft](https://visualstudio.microsoft.com/xamarin) and [Flutter (Dart) from Google](https://flutter.dev), which doesn't tradeoff development speed for: application runtime overhead; debuggability; testing; best-practice, and extensibility. Additionally, *CDD* also handles backends.
Code natively: [iOS (Swift)](https://developer.apple.com/swift); [Android (Java)](https://developer.android.com/reference); web ([Angular: TypeScript & HTML](https://angular.io)); backend (Rust: [actix](https://actix.rs) & [diesel](https://diesel.rs)). Translate model changes automatically across—and within—language boundaries. 36× speedup.
#### Designer
Similar to [Microsoft Access](https://products.office.com/en-au/access) and [Google Forms](https://gsuite.google.com.au/intl/en_au/products/forms), *[the designer](https://github.com/offscale/model-designer-rfc/blob/master/rfcs/index.md)* allows non-technical *creator-users* to create model-driven workflows for their *end-users*.
Builds upon [CDD](#compiler-driven-development-cdd) base and CI/CD pipelines, to enable release of new applications (backend, web to DNS names [possibly on a CDN], native mobile apps to app stores), all at the fingertips of the *creator-user*.
Engineers can then optimise and extend what's created, as it's all statically generated best-practice conforming code.
Concrete schemas also have significant advantages for data-analytics, especially on the performance side.
---
## Inspiration
Conceptual similarities can be found from our major competitors, in particular: [HashiCorp](https://www.hashicorp.com); Mesosphere; Flutter; and Google Forms.
HashiCorp probably does it best, with different websites for each product, and a central website showing them all. Each product in their suite can be used independently, most are open-source, and their themes are variations of the [master](https://en.wikipedia.org/wiki/Web_template_system).
*[Consul](https://www.consul.io); [Serf](https://www.serf.io/); [Terraform](https://www.terraform.io); [Vagrant](https://www.vagrantup.com); [Vault](https://www.vaultproject.io); [Packer](https://www.packer.io); [Sentinel](https://www.hashicorp.com/sentinel); and [Nomad](https://www.hashicorp.com/products/nomad).*