Everything these days is a blah-blah-as-a-service, and your development lifecycle should be no different. When you provide a well working and documented services that your team can use to provision resources and introduce change in a controlled way; you will enable your teams to innovate and focus on building value for your customers. How do … Continue reading DevOps Culture: Self-Service-as-a-Service
Automation is one of the key principles of a strong DevOps culture because it has such a high return on investment. How can you be confident in your software unless you’ve had a real person validate it? We continue the DevOps Culture series with discussing how automation takes your team’s confidence beyond the commit and … Continue reading DevOps Culture: An Automation-First Mentality
DevOps is a software development practice that specializes in the frequent delivery of software features and improvements. Through rapid integration of changes and receipt of feedback we build a culture of confidence and reliability in the software lifecycle. Additionally, teams that follow these practices are highly productive for their organizations and themselves. Successfully employing “DevOps” … Continue reading The DevOps Culture: Empowering Your Team
Stelligent CTO, Paul Duvall and Chief Architect, Casey Lee presented the top five DevOps related services and features announced at or prior to re:Invent 2017. Along with the features significance to the DevOps community. In case you missed this AWS re:Invent 2017 DevOps Re:Cap webinar, you can catch it here. DevOps related services and features … Continue reading AWS re:Invent 2017 DevOps re:Cap Webinar & Resources
re:Invent is just around the corner (next week!), which means a bunch of new services and features will be announced, and they probably won’t have CloudFormation support for a few weeks. As the biggest CloudFormation fanboy of all time, this is probably the most difficult time of the year for me, as I want to use all the new goodies but feel kinda icky not … Continue reading Lambda Backed Custom CloudFormation Resources
Imagine if an organization could construct chatbots with refined common dialect preparing and no operational overhead. Amazon Lex can be described as a fully managed service for building conversational interfaces into application using voice and text. Lex is integrated with AWS Lambda, a service that allows code to run without the provisioning or managing of servers. Lambda enables companies to write and run logic for your chatbot using serverless compute. The implication of bots into the conversation gives operations teams … Continue reading Using the $Latest Amazon Lex Alias
The annual Amazon Web Services conference, re:Invent took place in Las Vegas, Nevada. With over 40,000 attendees this year re:Invent 2017 was the biggest yet. With the sheer volume of activities and sessions that went on throughout the week, it was tricky to know where to invest your time. Stelligensia presented four sessions with various … Continue reading Stelligent Sessions at re:Invent 2017!
Simple dashboard built for viewing pipeline metrics in AWS. Built using CloudWatch dashboards and metrics populated from CloudWatch events that CodePipeline triggers.
Everyone talks about unit and functional tests when adopting Devops practices, but how do you know if one of your changes has introduced a major performance degradation? Performance testing is the missing link to having a truly Continuously Deliverable pipeline. In this blog post, you will see how performance tests can be integrated into your Continuous Delivery … Continue reading Performance Testing In a Continuous Delivery Pipeline
Previously, we covered the release of Yarn, a new package management system designed to fix some of the shortfalls associated with npm. With improvements in speed, efficiency, readability, and dependency management, Yarn has shown itself to be a worthwhile tool. In this post, we will put that tool to use and show just how powerful Yarn can be. Before we can demonstrate its potential, we have to … Continue reading npm vs Yarn: Part 2