Today we are delighted to be recognized as having achieved AWS Service Delivery Partner status for Amazon Aurora. As you can see from thenews release we issued, the AWS Service Delivery Program is designed to highlight AWS Consulting Partners who have a track record of delivering verified customer success for specific Amazon Web Services (AWS) products.
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.
Struggling to find and keep skilled resources? Or, interested in helping your team become AWS experts? Our very own Aater Suleman was recently interviewed by SearchAWS on the topic of getting the AWS skills you need this year. As Flux7’s primary goal is to help its customers fill an internal skills gap by educating them as we shepherd them through their DevOps and IT modernization projects, we were honored to weigh in on this important topic. While there were two primary recommendations made in the article, we have several others we’d like to add for a deeper look at this topic.
To support the business as best as possible, it’s important for Development to issue new features -- or greenfield solutions -- to market as quickly as possible. It’s not a stretch to say that many organizations’ ability to compete successfully depends on their speedy delivery of new products to customer. And in some cases first mover status is the difference between owning a market or bowing out of one.
One of the approaches our AWS Consultants consistently take is Security by Design. By building security in from the beginning--rather than as an afterthought--security rules, processes and controls are inherent to the system. We like to think of it as a race car with the roll cage built into the frame vs. a race car built and the roll cage added afterward. Truthfully, which car would you feel safer helming?
We have been working closely with a customer who is undergoing a business transformation. As a multimedia equipment manufacturer, the organization has a loyal following of its high quality devices. However, like many companies facing the convergence of markets and new customer demands, the company has embarked on a metamorphosis. Traditionally very focused on hardware, their software was largely ignored even though it offered customers real value. Part of the company’s transformation was a move to treat their software like a full-fledged offering, rather than a free supplement. An upcoming product release marked the first (and biggest steps), in cementing this change in company direction.
There are many reasons an organization might choose Amazon Aurora over the Amazon Relational Database Service (Amazon RDS). Superior performance, greater scalability, and the ability to restart without losing cache are just a few. However, for those organizations who are already running an important application or Website on top of the RDS managed service, it can be a challenge to migrate from it to Aurora, despite the latter’s obvious benefits. After all, you can’t just take down a service that customers expect access to 24x7.
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.
Last fall we asked if you would consider voting for Flux7 in Modern Infrastructure magazine’s annual Impact Awards. We truly value this award as it is given by the community to the companies that they value most in their journey to DevOps and IT modernization. Thank you for voting and naming Flux7 as the winner in the 2017 Best AWS Partner/Consultant Category.