docs

Information about API Foundation

What API Foundation is?

logo

API Foundation provides solutions for building applications and services in any environment. The Foundation API based on shell scripts that allow you to retrieve, manage and publish Your data to various display services, run geoprocessing models, and more. Our workflow in SOftware Development is clear:

Modularisation -> Standardisation -> Automation

it’s a Continuous Improvement, never end development.

Why API Foundation?

API Foundation Service has been developed as a best practice to integration capability of software, to give end customers the best product and service!

Bring your creative vision to life with APIfoundation tools.

Alternative way

May be You are using in Your organisation many different solution, may be one cloud based.

How old are these technologies, what can be after 10 years?

If You are creating serious software for long term, the perspective is very important.

That’s why API Foundation is not creating new tool, just using the old school tools in beauty way, because
the quality is for us very important and we expect long-term solution, which is not just popular solution for today!

If You are looking for long term solutions the standards are clear, what you can just make better are standards of usage it, such testing

For us is clear that we need solution for whole our (not just application) life.
It can take next 50 years for support API Foundation solutions.

We know it and we are ready for it!

Nobody knows, so the best what we can do now is to prepare the ecosystem with understandable and tested solutions for decades.

The roles are clear:

Simplicity

The KISS principle states that most systems work best if they are kept simple rather than made complicated;
therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided.
The phrase has been associated with aircraft engineer Kelly Johnson.
The term “KISS principle” was in popular use by 1970.
Variations on the phrase include:
“Keep it simple, silly”, “keep it short and simple”, “keep it simple and straightforward”, “keep it small and simple”, or “keep it stupid simple”.

Transparent (for everyone)

Opened (for The Future)

Benefits

native interface, code, environment

api-foundation-plants.png

Why do we think our solution is the best? Because we never create plastic entities, pseudo-languages. We base projects with standard standards, APIFoundation provides them in a modularized form.

What we offer You?

We Love Software Development and we create the best solutions with pleasure! We are able to create the best solutions, because we have deep understanding of technology based on advanced projects. We are earning money on trainings for teams which are opened to increase quality of software development at any time. We are independent and free to create the best IT solutions on the World!

Example of wide spectrum on technical side

if You need solve technical problem based on Python/Java/NodeJS, many solutions are based on one language. In APIFoundation case we are supporting and providing for each language the same SDK solution, which
avaliable to use in your application programming language.

Who give you the opportunity to use your own technical solutions in external libraries? We’re opened and we’re giving You opensource code which is ready to set and go!

No license, no subscriptions, ready to use!

How we understand an API

An application programming interface (API) is a computing interface which defines interactions between multiple software intermediaries. It defines the kinds of calls or requests that can be made, how to make them, the data formats that should be used, the conventions to follow

API (od ang. application programming interface)

Today, with the rise of REST and web services over HTTP, the term is often assumed to refer to APIs of such services when given no other context (see the Web APIs section).

The term API is, by extension, used to refer to the subset of software entities (code, subcomponents, modules, etc.) that serve to actually implement the API of some encompassing component or system.

A + (number) PI = API

API logo

API Foundation solutions

Apibuild1

APIbuild

apibuild-logo.png

https://github.com/api-build

procesy określające kolejności powstawania nowych wersji oprogramowania, pozwala na odróżnienie wersji między sobą.

Zazwyczaj jest liczbą naturalną (np. numerowanie wersji od 1 lub według roku powstania), liczbą rzeczywistą lub zestawieniem kilku liczb naturalnych. W ostatnim przypadku kolejne liczby oddziela się zazwyczaj kropką, a ich znaczenie jest następujące:

Responsibility:

APIunit

apiunit-logo.png

https://github.com/apiunit

definition of application for generating project on environment with source code

Responsibility:

APIfunc

apifunc-logo.png

https://github.com/apifunc

The environment for code execution of one simple function for any programming language from the list:

Responsibility:

APIsql

apisql-logo.png

https://github.com/apisql

Data integration for models statements

Responsibility:

APIcra

apicra-logo.png

https://github.com/apicra

library of shell scripts

Responsibility:

APIexec

apiexec-logo.png

https://github.com/apiexec

runner for APIcra scripts

Responsibility:

Apibuild2

The projects are using API Foundation solutions

DevOpsTerminal

devops_terminal-cube-green-128.png

https://github.com/DevOpsTerminal

Console Client with WebUI to acces by SSH many servers

Responsibility:

Components:

ProMaGen

13/cover.png

https://github.com/promagen

Project Manager & Generator is WebUI client installed on selected server to acces Customers on own projects, by executong defined shell scripts

Responsibility:

Components:

FaaS.ovh

4/cover.png

it’s a simple open solution for public FaaS

Responsibility:

Components:

Softreck’s API Foundation

The API Foundation is created and sponsored by the Softreck from Estonia. Softreck Company is sharing tools to give Organisations more benefits, to have under control all steps in software and Hardware Development.

Leadership through software development

At Softreck, we strive to go beyond securing smart technical resources by aiming to become your strategic advisors, providing both thought leadership and best practice to ensure that you are confident in being able to deliver solid results in less time and increase your ROI (Return on Investment).

Team

That is why our specialised team is built with the right mix of highly skilled architects and consultants, supported by management with years of industry experience.

Capabilities and requirements of application

The selection and deployment of an initial production API capability is used to prioritise and showcase the baseline platform, whilst delivering a tangible benefit to the business through better alignment and communication of capabilities and requirements.

Monitoring and report

Another key deliverable is a detailed report and executive presentation that provides Softreck’s assessment for the customer’s desired connectivity/integration platform maturity.

Our Help

We use technology such as Open API and Deep-Link connections, we can integrate that service into your business platform.

Whether it’s through embedded technology or something as simple as a booking widget, your clients can now access our booking system directly. We’ll even offer you a return on any reservations made.

Turning a clever feature into a profitable solution.

HOW TO START?

You can exercise all of the Foundation API methods through the API Console as well as view documentation and descriptions of the inputs and outputs of each API method.

Solutions

We started in 2018 with few concepts but one idea: fastest development. Now, in 2020 we are giving solutions:

Our Plans

We are preparing cloud solution, a FaaS implementation of our current environment solutions:

For private, company private API with authorisation we preparing the FaaSapp platform

Another solutions

Tekton

Tekton is a powerful and flexible

open-source framework for creating CI/CD systems,

allowing developers to

build, test, and deploy

across cloud providers and on-premise systems.

Get started with interactive tutorials.

Spinnaker

Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.

Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.

CI Integrations

Listen to events, collect artifacts, and trigger pipelines from Jenkins or Travis CI. Triggers via git, cron, or a new image in a docker registry are also supported.

Monitoring Integrations

Tie your releases to monitoring services Datadog, Prometheus, Stackdriver, SignalFx, or New Relic using their metrics for canary analysis.

CLI for Setup and Admin

Install, configure, and update your Spinnaker instance with halyard, Spinnaker’s CLI tool.

Deployment Strategies

Configure pipelines with built-in deployment strategies such as highlander and red/black, with rolling red/black and canary in active development, or define your own custom strategy.

VM Bakery

Bake immutable VM images via Packer, which comes packaged with Spinnaker and offers support for Chef and Puppet templates.

Notifications

Set up event notifications for email, Slack, HipChat, or SMS (via Twilio).

Role-based Access Control

Restrict access to projects or accounts by hooking into your internal authentication system using OAuth, SAML, LDAP, X.509 certs, Google groups, Azure groups, or GitHub teams.

Manual Judgments

Require a manual approval prior to releasing an update with a manual judgement stage.

White-listed Execution Windows

Restrict the execution of stages to certain windows of time, making sure deployments happen during off-peak traffic or when the right people are on hand to monitor the roll-out.

Chaos Monkey Integration

Test that your application can survive instance failures by terminating them on purpose.

Introduction to Vercel - Vercel Documentation

Introduction to Vercel

​Vercel is a cloud platform for static sites and Serverless Functions that fits perfectly with your workflow. It enables developers to host Jamstack websites and web services that deploy instantly, scale automatically, and requires no supervision, all with no configuration.

Deploy an Existing Project

Once you have signed up to Vercel, you can use our Git Integrations with GitHub, GitLab, or Bitbucket to deploy an existing project – then with a deployment for every push – by selecting a repository from your Git account.

Select a Git provider below to get started deploying your existing repositories and projects:

GitHubGitLabBitbucket

Connect through the “Import Project” page under the “From an existing project” section, and then from the same place, set up a project using your Git Integration.

Note: For more information on setting up Git to deploy with Vercel and what you can do with it, see the Git Integrations documentation.

Alternatively, if you want to start fresh with a new project, use a Quickstart template from below. Additionally, you can use this method to start a new Git repository with any connected Git Integration.

Jenkins X - Cloud Native CI/CD Built On Kubernetes

Accelerate Your Continuous Delivery on Kubernetes

Jenkins X provides pipeline automation, built-in GitOps, and preview environments to help teams collaborate and accelerate their software delivery at any scale.

API approach

The Benefits of an API-First Approach An API-first approach to building products can benefit your organization in many ways. And API first approach requires that teams plan, organize, and share a vision of their API program. In API foundation we build and share many tools that support an API first approach.

start API

Web APIs have been around for nearly 20 years. Form past few years are using defined concept of “API first” has gained traction with software teams.

Current

The number of developers taking an API-first approach to building products is rising. So today we thought we would introduce you to the concept of API first and why this approach is growing in prominence.

What Does an API-First Approach Mean?

That everything about a project revolves around the idea that the end product will be consumed by mobile devices and that APIs will be consumed by client applications.

language

An API-first approach involves developing APIs that are consistent and reusable, which can be accomplished by using an API description language to establish a contract for how the API is supposed to behave.

contract

Establishing a contract involves spending more time thinking about the design of an API. It also often involves additional planning and collaboration with the stakeholders providing feedback on the design of an API before any code is written. The Growing Popularity of API-First

data consumption

Today, both humans and machines are consuming data. Humans consume data through applications, often from many different devices — smartphones, laptops, tablets, and desktops. Many different types of devices mean many different screen sizes. Organizations must build apps that look good and work well across all devices.

strategy

An API-first strategy allows organizations to build APIs that serve all applications and applications can be developed and maintained efficiently for all devices, platforms, and operating systems.

Benefits

Development teams can work in parallel with many apps, backend, frontend, devops

contract first

API first involves establishing a contract. Creating a contract between services that is followed by teams across an organization allows those teams to work on multiple APIs at the same time. Developers do not have to wait for updates to an API to be released before moving on to the next API. Teams can mock APIs and test API dependencies based on the established API definition. Reduces the cost of developing apps.

modularisation

APIs and code can be reused on many different projects. When a development team wants to build a new app, they don’t have to start from scratch which is time-consuming and costly. API-first design also allows most problems to be solved before any code is even written which helps prevent problems when it is time to integrate APIs with applications. Increases the speed to market

Automatisation

Much of the process of building APIs can be automated using tools that allow import of API definition files. Our tools allow import of API definition files, and with those files API tools such as API documentation, SDKs, and mock APIs can be auto-generated. Automation significantly speeds up the development of APIs and applications.

benefits such on flat architecture

API first also makes it possible to add new services and technologies to applications without having to re-architect the entire system. The competition is fierce when it comes to developing applications, so apps must be developed quickly.

Ensures good developer experiences

Consumers of APIs are most often developers, and developer experience (DX) can make or break the success of an API. API first ensures that developers have positive experiences using your APIs.

learning curve

Well-designed, well-documented, consistent APIs provide positive developer experiences because it’s easier to reuse code and onboard developers, and it reduces the learning curve. Reduces the risk of failure

For most companies, APIs are used in nearly every business process — from marketing and sales to communication and consumer-facing applications, which means that APIs can impact every part of your business positively or negatively. API first reduces the risk of failure by ensuring that APIs are reliable, consistent, and easy for developers to use.

How to start?

Brainstorm

First, it is necessary to identify key services your business offers and capabilities of the business.

Establish API stakeholders

Who are the stakeholders within your organization? As many people as possible should be involved in your API initiative – you need company-wide buy-in and a vision that is shared by teams within your organization. Also, allow stakeholders to weigh in on the design of the API. Stakeholders can then agree on interactions across the organization so that APIs remain consistent.

Design an API contract, Consistency is key

Create a style guide

Implement API governance

Automate processes

Track and manage your API portfolio

Create a portal for internal developers

Tools online

SVG

https://vectr.com/tmp/f1tTRERgJD/gB3wURKki

https://editor.method.ac/