Draft:Systemless
Submission declined on 13 December 2023 by KylieTastic (talk).
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|  |
SystemLess on cloud services[edit]
While a System is "(...) an assemblage or combination of things or parts forming a complex or unitary whole, (...) or (...) any assemblage or set of correlated members (...)", [1](according to dictionary.com), the term systemless would be associated for a non-planed component, package, structure or assemblage, in which would be referred for a chaotic service.
However, just like several terms in software engineering and cloud computing like serverless services, Systemless means a cloud architecture deployment, supported by multiple automated services, in which can include low code or serverless services, that allows the engineering teams to create platforms, components, features or applications without investing much time on planning their own architecture.
There has been some attempts to create Systemless as a product like Systemless root from Chainfire [2] [3] which doesn't designate directly the purpose of the meaning, besides just another system more effectively, do not create any special bypass system where planning is reduce. However there are several attempts on software published in GitHub of trying this perspective of reduce effectiveness towards the low-planning-to-operation process.[4], nevertheless, still limited to software and try outs.
Imagine that in the near future of today at 2023, companies or new developers require BackEnd developers with good cloud computing knowledge to set up a cloud infrastructure to the Software as a Service (SaaS) product. A systemless product, in this case would recognise, set up and deploy the (SaaS) in a cloud provider without any planning, knowledge or time.
Let's take an example of the process, imagine a SaaS that requires a Database and a FrontEnd monolithic service would be deployed in a cloud provider like AWS [5]. The systemLess would simply analyse the structure of all routes of the app, would find out that it is a monolithic service, would define the best service, like Lambda or Fargate or the direct use of EC2 instances, would further analyse if need to create certain services to Latency or security or other, and deploy according to the owner need. Currently, at this time, it is a possible process, just not yet created in 2023. The latest developments for Artificial intelligence like openAI [6]are proof that it is possible to create applications and products just by explaining what we want or what we need.
References[edit]
- ^ "System". dictionary.com. Dictionary.com, LLC. Retrieved 24 October 2023.
- ^ "Chainfire". chainfire.eu. Chainfire. Retrieved 13 December 2023.
- ^ "CopyProgramming". copyprogramming.com. CopyProgramming. Retrieved 13 December 2023.
- ^ "GitHub systemless topic". github.com. GitHub. Retrieved 13 December 2023.
- ^ "AWS". aws.amazon.com. AWS. Retrieved 13 December 2023.
- ^ "OpenAI". openai.com. OpenAI. Retrieved 13 December 2023.
- in-depth (not just passing mentions about the subject)
- reliable
- secondary
- independent of the subject
Make sure you add references that meet these criteria before resubmitting. Learn about mistakes to avoid when addressing this issue. If no additional references exist, the subject is not suitable for Wikipedia.