What is Architect?

The architecture and development of cloud applications has become extremely complex in recent years, and just about everyone has adopted service-oriented architecture or microservices to some degree in their applications. Despite this widespread adoption however, cloud-native development still lacks the basic tools needed to enable developers to collaborate and connect with one another safely and efficiently. We use dependency and package managers to connect to and extend software components every day in our favorite languages and systems, so why not collaborate across cloud services as well? Architect is the platform that brings this much needed collaboration to cloud-native development - enabling developers to follow already familiar patterns to connect to dependencies and build upon each others' work.

Unlike with traditional package managers, dependencies for cloud services cannot be resolved at build time with a simple download of components. Since each service needs to be run independently before they are ready to respond to requests, these relationships must be brokered at deploy time. Architect's platform not only serves to index and distribute access to service artifacts, but also to ensure that related services are deployed in concert and can immediately connect to one another. No matter what the underlying platform or networking tools, Architect ensures that any service ships alongside its dependencies enabling true component re-use and seamless integration.

How does it work?

Architect is effectively a combination of a dependency management solution and a deployment platform - enabling services to be published, shared, and discovered (both publicly and privately), while also enabling services to be deployed to a variety of environments and cloud platforms. Services are much like their component counterparts in package management in that they consist of artifacts paired with a manifest file outlining the services name, interface, and dependencies. In order for these services to be used however, users must also configure one or more target environments to which the artifacts can be deployed. Architect acts as the funnel ingesting services and shepherding them into these registered environments.