In 2013 Gene Kim, Kevin Behr and George Spafford published The Phoenix Project, a book that marries the concepts of manufacturing agility from Eliyahu Goldratt’s The Goal and relates them to IT. As they elucidate in the story, a new approach to IT is clearly needed and many organizations are embracing that change through the DevOps methodology. However, DevOps can be a very broad term making it difficult for people to know where to begin. As a result, we have narrowed the DevOps model
I recently read an article asking, “will IoT save retail”? Indeed, there are several ways IoT can help address issues that keep many retailers up at night. From RFID to help with supply chain cost efficiencies to Beacons that serve to increase marketing and sales outcomes, IoT initiatives are being heavily invested in across retail segments. Moreover, IoT is just one example of an area where digital transformation can help retailers become more competitive and better match their products and services to evolving customer expectations.
Whether you are serving consumers visiting your website or internal customers accessing infrastructure services, customers want the ability to access what they want when they want it. As a result, scalable architecture is top of mind for many organizations -- especially those who face peaks in traffic and must be able to effectively service it. Designing for scalability, the ability to handle large amounts of traffic and service it gracefully, without degradation of performance or downtime, is an essential component of successful service delivery.
An ounce of prevention is worth a pound of cure, and, that’s exactly what this SaaS sales application provider asked for the AWS experts at Flux7 to come in and provide. Knowing our deep background and knowledge of the ins and outs of AWS services -- and the ecosystem of technologies that work with it -- they asked if we could validate their AWS roadmap and help them take full advantage of the benefits AWS provides.
As an Austin, TX based DevOps consulting firm, we work often with organizations in the energy space, empowering them to directly address business drivers and see their ideas come to life with the application of modern technology. So it was in this vein, that we were approached by a publicly traded, global solar company who wanted to use a cloud migration as an opportunity to overhaul its business processes. (You can read the full case study here.) Specifically, they were looking to use the opportunity to grow developer agility, gain global access for their workers and to save on capital expenses while maintaining compliance and building-in standardization.
While microservices benefit a variety of organizations on multiple fronts, (for a deeper discussion on this, please check out our blog, “Microservices Trend as IT Competes on their Respective Strengths”) today we are examining how one startup used a microservice architecture to give developers greater agility and add automation to gain a competitive advantage in its industry.
AWS recently announced that Amazon ECS now supports a state for container instances that can be used to drain a container instance in preparation for maintenance or cluster scale down. AWS reports that the draining state prevents new tasks from being started on the container instance and notifies the service scheduler to move tasks that are running on the instance to other instances in the cluster. This is great news that we expect to save a lot of time and scripting when it comes to updating or removing containers from a cluster.
Container technology was a well-read topic on the Flux7 blog in 2016, joining our blog on Continuous Integration Best Practices(CI/CD) and AWS Configuration Management as subject areas that received the most attention from our readers. From hardening containers to container based cloud migration frameworks and Docker-based microservices architecture, our DevOps consultants published a great deal of analysis, advice and best-practice approaches to help our readers achieve success with containers in AWS.
Continuous Delivery (CD) is a core facet of successful DevOps and as a result, a core Flux7 strategy for implementing DevOps-based IT modernization. At Flux7, we always view DevOps as streamlining the delivery of not just Code but also the delivery of Infrastructure (networking, firewalls, VMs), Server Configuration (software packages such as Apache or JAVA), and Security Rules (policies for AWS Config Rules or HashiCorp Vault). Among these, efficient delivery of infrastructure and configuration are both very critical for full stack agility. For our customers in AWS, our typical choice for infrastructure delivery is CloudFormation. We like AWS CloudFormation because it is native to AWS, follows a simple YAML or JSON syntax, and has deep integration with other AWS Services such as the AWS Service Catalog.