Each component of the application can be managed independently. ... At the core of Cycligent is a technology called Holo
Cycligent Simplifies the Transition to Microservices The leap from legacy system to a more agile microservices architecture is not always a simple step. There are some best practices and patterns that must be in place before you can start segmenting your monolithic application. Cycligent allows for teams of any size to fully jump into Microservices, fulfills many of the prerequisites necessary and simplifies the process of implementing Microservices.
Step 1: Creating and Managing the Microservices Infrastructure with Cycligent N-Tier Architecture Upon signing up, Cycligent pre-configures a completely adaptable n-tier architecture. This is complete with connected database, workers, long workers, load balancing, message buses, and other components removing the burden of configuring a complex infrastructure. The infrastructure is completely adaptable and resource management can be done within Cycligent’s UI. This allows for any combination of resources to be created and utilized for a microservices architecture. No coding and no additional configuration.
Cycligent automatically configures a production, QA and Development environment for you. These are completely configurable and customizable by clicking on the settings wheel and making adjustments that make sense for your project.
Page 1
www.cycligent.com
®
Resource Management Cycligent makes manipulation of servers and other resources very simple and open. Cycligent provides auto-scaling, routing configurations, and the ability to increase, decrease, start, or stop individual servers via the Cycligent UI. Each component of the application can be managed independently. This means that each microservice can be scaled up or down independently manually or using the auto-scaling features. Additionally, Cycligent gives complete remote access to each server for custom configuration. Essentially, Cycligent automates the process of building the underlying microservices infrastructure and yet gives full control of all resources where custom configuration is required.
Page 2
Step 2: Automated Build Process Cycligent automatically creates a Dev, QA, and Prod version type for developers. If desired, additional testing environments can be created such as a canary environment. Once set up, the development team can move each microservices through independent deployment pipelines which are completely separate from one another. Cycligent automates the build and deployment process through the deployment pipeline. Simply upload your files, or point to your GitHub repos and then click deploy. When integrated with GitHub, the moment that a developer checks in their code a build process is automatically initiated. The build process goes through a series of automated tests. If the build fails, Cycligent provides logs of the build process in order to determine the point of failure. If the build succeeds, the application can then proceed through the deployment pipeline.
Page 3
Step 3: Version Control System Via Microservices Approval UI The entire team can also take advantage of Cycligent’s microservices version control. Once the build process completes, Cycligent provides a Microservices Approval UI which allows a manager, client, project manager or developer to act as a gatekeeper allowing only approved changes to be pushed to a production environment. Whoever has approval access will be able to see what has been built and by which developer via the approval screen, giving complete control over the process. When ready, a developer can select the changes that should be deployed and use Cycligent’s 1 click deployment process.
Page 4
Step 4: Automated Deployment The application or changes to an application can be deployed using Cycligent’s 1 click deployment process. At the core of Cycligent is a technology called Holographic Hosting. This technology allows for developers to deploy their code and it then be distributed (like a hologram) across all servers within a distributed system. No modification to the code is required.
Page 5
Step 5: Continuous Delivery and Multiple Versioning One of Cycligent’s most unique offerings is the ability to deliver multi-versioning capabilities. Within the pre-configured Cycligent environment, Cycligent automatically provides a Dev, QA, and Prod version type. However, development teams can add additional environments to facilitate multiple versions of an application. This provides a platform to perform continuous delivery patterns such as blue/green deployment or canary release. For example, teams can have two production versions of their application running simultaneously on the same URL or URL path. If a particular component of the microservices application needs to be tested “in the wild,” the application can be pushed to one of the production environments containing only a subset of users. When ready, the component can then be deployed to the rest of the users with zero-downtime. This provides a seamless transition when deploying new features and minimizes the risks associated with deployment.
Page 6
Cycligent’s User Interface Cycligent allows users to manage their cloud infrastructure all from one user interface. Other platforms require page after page of configuration. Cycligent simplifies the process and keeps everything centralized on the “Cloud Control” page.
Page 7
www.cycligent.com
®
From Monolith to Cycligent’s Microservices Platform Cycligent solves some of the more complex issues faced when moving to a micorservices platform and eases the transition from a monolith architecture. If interested, you can get a free 30 day trial (no credit card required), and/or request a full demonstration of Cycligent in action. Additionally, we make the transition as seamless as possible, offering 1-on-1 support throughout the lifecycle of your project.
Request a Demo
Start a Free Trial
Connect with us:
www.cycligent.com
Call us: (866) 865-9292
[email protected] 
