BUDDY; OUR LIFE; OUR HOPE.

The unavoidable problems that are dreaded by developers and organisations in developing world-altering Apps and services are the large amount of time invested into accomplishing a task, the huge cost, complexity of infrastructure and the day to day maintenance. The challenge posed by parallelism cannot also be overlooked. Most times the consequence of these problems is that ample time for developers to concentrate on the core of the project is not at their disposal. Also, in the blockchain technology, some problems arise for both starters and experienced off-chain developers, this is becaue programmers must have a good understanding of how some concepts like blockchain, EVM, solidity and Gith work, this whole processes make contracts get complex and the non-simplicity of the blockchain technology education may attracts bugs and flaws into the system with the attendant consequences on cryptocurrency( a huge loss may be recorded).

Another bane of blockchain is the lack of tool to foster trust between project founder and their developer, this deficiency has made entry into blockchain by developers a non-attractive desire.

But the goodnews is that Buddy has come to ease developers and or the users of the challenges poses by these problems, if I am to describe Buddy concisely, I would say, they are problem sharers and problem solvers or simply put a soulmate.

Buddy in its non-literal meaning is an application development and deployment platform that have not only proffer solutions to developers problem and problems associated with blockchain, it has also come up with advances that will be useful in the nearest future. Buddy is promoting specialisation and
Buddy could say it is encouraging focus in that organisations now focus on "shipping" which improves their automation metrics to promote business.
Thanks to buddy team for attracting developers to blockchain and making the community grow bigger and better, they have made this possible by demystifying blockchain technology.
As we go through the solutions proffered by
Buddy, it is evident that they have come as a helpmate not only to the developers but also to non-developers, users and third party.

DECENTRALIZED DEVELOPMENT AUTOMATION PLATFORM

To avoid repetition of the problems aforementioned in the introduction, let me quickly say that the core aim of
Buddy in this aspect is to afford organizations with the opportunity of avoiding the redudant part of development and deployment, the goal here is to allow them focus on shipping, which is where the business value lies.
Buddy team has come up with three feasible solutions which shall be discussed below

Buddy SOLUTIONS

1. The DevOps marketplace
2. Private automation GRID
   3 .Shared automation GRID

The DevOps marketplace
This is a platform where developers, third party developers and users interact. Through the development of automation actions, building, testing and deploying can be done quickly, it is a chain that is open to third party developers to operate, where actions not originally in the market place could be integrated into it and executed. An example of a third party action is the securify that allows for automated analysis of any ethereum contract for critictical security vulnerability and insecure coding through a web, the good thing about the securify is that it increases code quality and reduces shipment time. Notable example of action by a third party is chainsecurity that runs paid chain security audits. Some notable marketplaces are Allassian and wordpress that hit $120million and $S73 respectively in 2015.
Third party developers do not submit their actions gratis, they are paid for the solutions they submit to the market place, publish plugins for free. Apart from the monetary value of the marketplace to third party developers, they can also rest assured that their intellectual property is protected from plagiarism. Non-commercial open source project can also use third party App without being charged.

PRIVATE AUTOMATION GRID

This depends on
Buddy instances that have the ability of auto discovery and replication to create high-availabiliy scalable infrastructure for development and deployment automation.

The advantage is that the user is in full control of the trusted infrastructure to use because he decides what to use to run
Buddy instances
It must be noted however, that the first two instances create a master-master replication before creating high availability system. The next instance is used as agent to run more pipelines in parallel thus speeding up delivery times and eliminates unnecessary queues.In a situation where the load demand is high buddy removes redundant instances and creates new ones.

SHARED AUTOMATION GRID
Here different users that run a network of
Buddy instances share high intensive automation task that is offloaded to the instances they run.
A compute unit is usually given in exchange for a BUD token by the instance owner.
2VCPus, 2GB of RAM and 4GB of SSD storage are those that pass the benchmark accepted by Buddy.

![IMG-20180731-WA0001.jpg](

WHY CHOOSE SHARED GRID OVER PRIVATE GRID?

It is advantageous to explore the shared automation grid in a task that requires the input of large resources in order to produce a fast result

*IS THE SHARED AUTOMATION GRID WITHOUT AN ADVANTAGE? Let's find out!!!

After the completion of a task in a shared automation GRID, each supplier is awarded a
Buddy token when the task is completed. However, the requester need not worry over the price because it is negotiable. The supplier also has the autonomy on the minimum price to sell, decide when to we compute unit and the price to give. The safety of the supplier is also guaranteed because the DevOps marketplace serves as a membrane that selects the action to be run on the shared automation GRID. Only actions that have been judged acceptable by curator are allowed to run, this measure protects the GRID against abuse.

What drives demand?

In order to improve demand for
Buddy compute unit and advance parallelism that ensures usage of additional resources outside the inbuilt network which speeds up delivery has been developed. In advanced parallelism, aactions in pipelines are divided into separate jobs that can run simultaneously.
Three levels are known

1. Project level
2. Pipeline level
3. Action level.

Project level: Many pipelines run at once, this prevents overloading of the available compute units as the number of compute units available is determined by the number of pipeline that can be run

Pipeline level: This raises the number of compute units because of running concurrent action within the pipeline. For example, in the running of 3 concurrent actions and 3 pipelines, 9 compute units are required.

Action level: This is the dividing of action into tasks running in parallel.

SONM and GRIM can't replace Automation GRID. Find out why

1. Automation by design: The services to run are inbuilt. It does not need the user to interact with it before a job can be executed I.e there's automatic execution of jobs and this removes the tedious process that the user has to go through in using a supercomputer and in fact very large computing power needs to be used

The use of fixed and local resources
The downside of using supercomputers is that they cannot handle tasks that are often resource intensive adequately. Due to resource deficit supercomputers cannot run task that require a hug resources. The fixed resources of automation GRID enables a third party to know what design to run because it gives an idea of the resources

Buddy shared automation GRID specialises in solving contemporary market need without delay. This is not possible on super computers which is more complex and do not put users project at risk.

However, in order not to put supercomputers at a total disadvantage, the good news is that Buddy is ready to integrate supercomputer-
Buddy actions inti their DevOps marketplace.
Buddy is also working in means to removing the
Buddy generated by utilisation of the compute unit within the pipeline to procesd actions by developing actions that can utilise their own power!!!

BuddyS INTERVENTION IN BLOCKCHAIN

Having identified the problems associated with blockchain technologies in the introduction,
Buddy has offered some visible solutions which eventually will attract developers to use the blockchain

The solutions offered are;
1.BlockchainOps
2.dAppOs

1. Distributed blockchain as-a-service

dAppPOs
dAppOs is a kind of development environment, friendly and accessible.It serves as means of advancing blockchain based project like dApps without external aids. This development also give room for the integration of services like MySQL, Reds etc into test.
dAppps can serve the following functions

DEVELOPMENT, PREVIEW, OR ENVIRONMENT

dAppOs can either work independently or adjuctively with a branch. When it works as a standalone it is used for development, testing and preview but when it works with a branch it supplies each branch with both instance and the services attached to it.
Wow!!! It please me to inform you that the working of dAppOs isn't limited to any locations and it is also available on user's private network.

dAppOs AS A TRAINING TOOL

IIt serves as a building block to smart contract/dApp projects uused in bblockchain training. This attracts users to the blockchain because it removes complexity faced by learners of blockchain development since it is training- oriented.

dAppOs AS TEMPLATE UNIVERSE

The template univsess is a marketplace for templates provided by 3rd party developers. This template is not without a merit because it gives room for contemporary blockchain technologies to be discovered and also ease testing.

The template provides easy interaction with the contract for non-programers, testers and clients can also use it to validate the business objectives of contract.

Distributed blockchain as-a-service

Buddy has encouraged specialisation cum productivity and efficiency in blockchain developers because developers now major on whatever task they need to achieve

Blockchains a la carte.

Evaluation of blockchain technologies by organization is key to making a smart decision that precedes production. With built-in dAppsOs templates for Ethereum, NEM and multichain development creating multi-chain application is easy and also developers are able to evaluate the multiple block chain application with ease

Through the solutuons ( BlockchainOps, dAppOs and distributed blockchain as- a-service) blockchain technology education is dymystifies ans there is a demand for large blochains as barriers that opposes participants are reduced

BUD TOKEN

The token used by
Buddy is a uitility token called BUD. Thus token increases usability of Buddy within the blockchain they represent. It creates new ecosystem that empowers the participant, and also givesvthr hokder a right to use the network and take advantsge of uts services to vote on the governance of its network and upgrade. This token helps to connect products and services without restrictions of location. A pictorial representation of the token pathway is below

![IMG-20180731-WA0015.jpg]

()

THE OBEJECTIVES OF THR TOKEN ARE AS FOLLOWS

1. To ensure security and transparency for the systems participant
   2.:To provide a true and powerful utility
2. To develoo strong economic incentuves
3. Ti enhance the platform with the network ownership effect
4. To stand as a source of governance

2-in-1 Expertise

Automation bots are used in DevOps marketplace for application and deployment purposes. Even thou these bots are driven using AI and machine learning, the experience, expertise and creativity offered by humans are incomparable. Burdy is advancing in solutiin development for expersts and advisors. This brings Buddy users and specialist together. The expert is also able to acrue income as it receives job orders daiky

Where do the funds go?

To fund the solutions proffered by Buddy in the decentralised and deployment platform, funds that are generated during the Buddy ICO are used .The funds are also used for advancing technologies for blockchain application development. Market succes and high token demand also depends on funds from ICO

Summary and Conlusion

I therefore submit that considering the fact that Buddy has greatly reduced the cons involved with Appd development especially Blockchain Appdev by the combinatin of different tools and techniques coupled with the strong partnership with world's strongest economu and determiner such as Google clouds,GitHubs and thr likes, the world is near perfection in facets of our civil life, commerce and even in the government of the nations of the world.

Meet our esteemed team

Simon Szczepankowski: CEO, product manager and co-Founder

Raphael Sztwiorok: CTO, Projecy Managr an Co- Founder

Thomas Korwin-Gajkowski: Blockchain solutiom Architect

Martin Kudla : Softwarw Architect and Co- Founder

Michael Hankus: Senior Software Engineer and Co-Founder

Thomas Prus: Senior Software Engineer

Alexander Kus: Chief Growth officer

Paul Olek: Head UX/UI & Co- Founder

Octavia Nowakowska: Head of Customer Support

Paul Kapala: Senior full Stack web Developer

Darek Sztwiorok: Java Developer

Lucas Czulak: Data Analyst

Chris Stryczek: Head of Test Engineering

Michael Bigos: Test Engineer and Technical Support Specialist

Patrick Trojanowski: Customer Support Specialist

Bart Piela: Front-end Developer

For More Information And Resources

Buddy Website
Buddy WhitePaper
Buddy OnePager
Buddy Token Sale
Buddy YouTube
Buddy BitcoinTalk
Buddy Facebook
Buddy Telegram
Buddy Linkedin
Buddy Twitter
Buddy Medium
Buddy Github

Buddy2018

This is my entry for the originalworks contest. you can join contest here