Those are services that replace parts of an existing system or are built on top of it and that can increase or decrease IT resources as needed to meet changing demand. Scalability is one of the hallmarks of the cloud and the primary driver of its exploding popularity with businesses. I am experienced in creating services using Amazon Web Services or Google Cloud and encapsulating them in Docker containers that can run inside K8s clusters.
Microservices are an architectural and organizational approach to software development where software is composed of small independent services that communicate over well-defined APIs. These services are owned by small, self-contained teams.
Serverless computing is a method of providing backend services on an as-used basis. Servers are still used, but backend services from a serverless vendor are charged based on usage, not a fixed amount of bandwidth or number of servers.
Containerization is a form of virtualization where applications run in isolated user spaces, called containers, while using the same shared operating system (OS). One of the benefits of containerization is that a container is essentially a fully packaged and portable computing environment. Everything an application needs to run — its binaries, libraries, configuration files, and dependencies — is encapsulated and isolated in its container.
A distributed system is a collection of computer programs that utilize computational resources across multiple, separate computation nodes to achieve a common, shared goal. Distributed systems aim to remove bottlenecks or central points of failure from a system.
My mission is to help clients transform complex ideas into elegant solutions
These services run inside Docker containers on AWS and are not overly complex, so they don't require a significant amount of time to create (1-2 months)
These services require complex orchestration and integration and are capable of handling large amounts of data. Development time could range from 2 to 6 months
These services are highly complex, designed for durability, and capable of scaling to support thousands of paying users. Implementation can take more than 6 months and the services are usually designed to run inside Kubernetes (k8s)