We are honored to be named for a third year running, a finalist in the TechTarget Modern Infrastructure Impact awards for Best AWS Consultant/Partner. This category recognizes the top consultants and integration partners in the field, those that consistently excel at creatively solving customer challenges through AWS services.
AWS has announced a new service that simplifies and streamlines the process of migrating existing virtualized applications to Amazon EC2. Joining AWS’s Database Migration Service and Service Discovery, AWS Server Migration Service simplifies the migration process by allowing users to incrementally replicate live VMs to the cloud, in the process removing the need for lengthy maintenance periods that previously may have taken critical systems offline longer than the business has tolerance for. In the process, AWS makes its service that much more attractive -- and sticky -- by allowing users to quickly and easily migrate to the cloud for free.
AWS has announced the arrival of a new US East Region in Ohio. This invokes two important questions for AWS users, namely is the new Ohio Region a better choice for my organization? And, if so, should I switch over to it? The answer to both questions really depends on where your organization is located. Let’s take a look at how you can practically examine the fit of the new Ohio Region given your specific location.
Enterprises are investing heavily in their IoT efforts, so much so that the total IoT market is expected to grow to $1.7 trillion by 2020, compared to its $656 billion in 2014, according to research firm IDC. The research firm Gartner estimates that there will be 8 billion business-connected IoT devices by 2020. With so many devices coming online, enterprises can expect a lot of changes and incremental demand on their infrastructure.
Those that do it right will be able to drive innovative solutions for themselves and their businesses. But what does such an innovative friendly IoT infrastructure look like? For that answer, we turned to Flux7 co-founder, Aater Suleman.
In our last article , we took a look at why Docker is a natural fit for microservices and the top five process design points to consider when planning for a Docker-based microservices deployment. Today we will dive into the top five technology design points that should be considered in the planning stages. Doing so will help you avoid potential stumbling blocks that when not thought through in advance can really cause headaches down the road.
As AWS consultants steeped in DevOps best practices, Docker, and the forward edge of new technologies and architectures, we often get asked about microservices. One of the most common questions we field is around potential stumbling blocks to a Docker-based microservices approach. This is a really smart question as there are several considerations that when not thought through in advance can really cause headaches down the road.
Before we talk through these top considerations, however, let’s first review why so many organizations are considering microservices in the first place. As you likely know, the idea behind microservices is that instead of writing an application as a single monolithic code base, developers can break it into smaller, autonomous services. This allows for more agility and greater autonomy amongst different teams, allowing them to work in parallel accomplishing more in less time.
Despite many of the valid concerns surrounding enterprise Internet of Things (IoT) deployments, there’s no slowing its momentum now. By some estimates there will be more than 50 billion intelligent and connected devices by the year 2020, and within a decade, according to a McKinsey study, these devices will spark $11 trillion in economic value. Despite uncertainty around return on investment, regulations, or the ability to execute because of technological barriers, the move to connect and add intelligences to disparate and distributed devices remains strong.
AWS launched EC2 Run Command in October 2015 to provide a simple way of automating common administrative tasks like installing software or patches, running shell commands, performing operating system changes, managing local groups and users, altering configuration files and more in Windows instances. AWS quickly followed the launch with the same feature for Linux instances, and in May 2016, they added the power to Manage & Share Commands, and the ability to use additional predefined commands along with any custom commands that users have created for their accounts.
In addition to the announced CloudFormation YAML support, AWS also announced cross-stack references for CloudFormation. (For Flux7 commentary on YAML support, please see our blog post earlier this week here.) As our AWS experts work daily with CloudFormation, we were very interested in this news and couldn’t wait to roll up our sleeves and take a look for ourselves.
