{"id":24746684,"url":"https://github.com/samuelmarks/brand-concepts","last_synced_at":"2025-03-23T01:23:41.412Z","repository":{"id":150265194,"uuid":"195538493","full_name":"SamuelMarks/brand-concepts","owner":"SamuelMarks","description":"Brand concepts for new websites, apps, and presentations","archived":false,"fork":false,"pushed_at":"2019-11-04T00:33:16.000Z","size":10,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-01-28T04:32:02.506Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/SamuelMarks.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-07-06T12:44:44.000Z","updated_at":"2019-11-04T00:33:18.000Z","dependencies_parsed_at":null,"dependency_job_id":"3058d0d6-814a-4be0-943a-d8801384d968","html_url":"https://github.com/SamuelMarks/brand-concepts","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SamuelMarks%2Fbrand-concepts","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SamuelMarks%2Fbrand-concepts/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SamuelMarks%2Fbrand-concepts/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SamuelMarks%2Fbrand-concepts/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/SamuelMarks","download_url":"https://codeload.github.com/SamuelMarks/brand-concepts/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245042148,"owners_count":20551525,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-01-28T04:30:12.142Z","updated_at":"2025-03-23T01:23:41.387Z","avatar_url":"https://github.com/SamuelMarks.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"brand-concepts\n==============\n\n[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.\n\n## Slogans/subtitles\nMay prove useful, may not, all original:\n- The IT infrastructure space is ripe for change. Docker, Kubernetes and friends have taken over the space, as have AWS, Google, and Azure.\n- Bring it to 1 laptop. Enable deployment from 1 node to 10,000. Any public or private cloud.\n- Build backend \u0026 apps, from 1 dev to many teams.\n\n- \"Because big companies don't look at small problems\"\n- \"We build what you promised\"\n\n## License\nAll 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.\n\nJustifications include—but are not limited to—increased:\n- **security**; interoperability (e.g.: OS, programming-language, protocol);\n- **extensibility**;\n- **community**: potential;\n- **standardisation**;\n- **onboarding speed**: no signing required;\n- **maintenance**: 1-off delivery for one client could mean long-term free upgrades, if the project is then used by other clients/companies/individuals;\n- **general quality**: especially with automated metrics, that can be advertised \u0026 integrated with Github/Gitlab;\n- **development speed**: can rely on libraries produced by others—as well as by us—to produce solutions faster;\n- **attractiveness**: engineers like the idea for various reasons, including above, building their portfolio, and freedom to share ideas openly \u0026 publicly.\n\n---\n\n## Principles\nScalable from 1 node to 10,000. Build low-level, functional, structures.\n\n### Performance\nWith 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.\n\n### Scaling on the low end\nOther [Mesos](https://mesos.apache.org/)-based solutions don't come close to 1 node usability. Really 5 minimum, 11 prefered minimum.\n\nA 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).\n\n---\n\n## Products\n\n### [CI/CD](https://en.wikipedia.org/wiki/CI/CD) pipelines\n[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)).\n\n#### [Dotfile](https://en.wikipedia.org/wiki/Dotfile) style\n*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); \u0026 other competitors*.\n\nTake any CI/CD config format as input, produce any as output.\n\nHave own format also, and a static binary that can run on this format.\n\nSo now you can self-host your own [CircleCI](https://circleci.com) competitor.\n\n#### [Mesosphere](https://mesosphere.com) style\n[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.\n\n### Compiler Driven Development (CDD)\nAn 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.\n\nCode natively: [iOS (Swift)](https://developer.apple.com/swift); [Android (Java)](https://developer.android.com/reference); web ([Angular: TypeScript \u0026 HTML](https://angular.io)); backend (Rust: [actix](https://actix.rs) \u0026 [diesel](https://diesel.rs)). Translate model changes automatically across—and within—language boundaries. 36× speedup.\n\n#### Designer\nSimilar 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*.\n\nBuilds 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*.\n\nEngineers can then optimise and extend what's created, as it's all statically generated best-practice conforming code.\n\nConcrete schemas also have significant advantages for data-analytics, especially on the performance side.\n\n---\n\n## Inspiration\nConceptual similarities can be found from our major competitors, in particular: [HashiCorp](https://www.hashicorp.com); Mesosphere; Flutter; and Google Forms.\n\nHashiCorp 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).\n*[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).*\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsamuelmarks%2Fbrand-concepts","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsamuelmarks%2Fbrand-concepts","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsamuelmarks%2Fbrand-concepts/lists"}