Containers are portable assets that let you design and deploy with little overhead from your development team. They take your monolithic code base and turn it into several lightweight modules that you can more easily manage and interconnect without worry of one small module taking out your entire application. This gives you more granular control of your code, but it also means that you have several moving parts as part of your platform.
Business owners are constantly searching for the next great technology that will help streamline solutions, improve workflow efficiency, and boost their ROI. Cloud computing has quickly become one of the most effective technologies in helping companies increase work output and cut costs.
Cloud computing has been around for so long now that cloud is basically a household word. Yet, despite how widespread cloud computing has become, continued adoption of the cloud is now being challenged by new types of use cases that people and companies are developing for cloud environments.
As time goes on, more and more organizations are abandoning the outdated waterfall development methodology for more practical and efficient Agile development practices. As this movement has occurred, development teams are moving faster than ever by employing Continuous Integration (CI) and Continuous Deployment (CD) practices that are serving to shorten development cycles and get new features into production with increasing speed.
Last week, at the AWS Summit San Francisco, AWS unveiled the new AWS Secrets Manager service. This new service allows you to: Save your secrets, passwords, and API keys in a KMS-encrypted storage service, Retrieve your secrets from your applications using the AWS CLI and AWS SDKs, and Automatically rotate your secrets on a custom schedule.
Due to its highly scalable nature, monitoring cloud computing is different from monitoring on-premise servers. The cloud vendor may have tools you can use, but if they fall short of your monitoring requirements you need to seek alternative solutions. Discover the right monitoring tools for your situation.
One of the most common business requirements data handlers face is the numerous data privacy standards present as industry standards. Each industry has their own variation, each with their own specific requirements — but regardless of the standard or the applied dataset, compliance is extremely important.
Throughout this series we have been exploring how to use serverless architectures to our advantage. In this article I will show you: How to create a serverless slack command using Node.js & Up, Best Practices when developing serverless applications, A curated list of serverless resources.
In Part 2: Serverless Scales I briefly touched on how a serverless architecture can have a cost benefit. In this post, I will go over: How to approach and analyze the cost of serverless, Two detailed examples of a cost analysis.
In Part 1: What is Serverless? I talked about how one of the biggest pros to a serverless architecture is how well it scales and how high availability is baked in. In this post I’ll go over: How a traditional highly available scalable architecture works, How a scalable serverless architecture works, How you can benefit from a serverless architecture.
