Search Results for "routing"

Micro addresses the key requirements for building services in the cloud. It leverages the microservices architecture pattern and provides a set of services which act as the building blocks of a platform. Micro deals with the complexity of distributed systems and provides simpler programmable abstractions to build on. Micro is the all encompassing end to end platform experience from source to running and beyond built with a developer first focus. Micro’s goal is to abstract away the...

GLBC is a GCE L7 load balancer controller that manages external loadbalancers configured through the Kubernetes Ingress API. Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource. An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting. An Ingress controller is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure your edge router or additional frontends to help handle the traffic. ...

Empire is a control layer on top of Amazon EC2 Container Service (ECS) that provides a Heroku-like workflow. It conforms to a subset of the Heroku Platform API, which means you can use the same tools and processes that you use with Heroku, but with all the power of EC2 and Docker. Empire is targeted at small to medium-sized startups that are running a large number of microservices and need more flexibility than what Heroku provides. You can read the original blog post about why we built...