How do you streamline the application deployment on Amazon Web Services? The process is simple with Media Temple on your side.
Short answer: Yes. The chances of people browsing your site are slim without an SSL.
By now, you’ve likely made the basic adjustments to working remotely: You’ve got the essential software installed, you’re starting to understand the point of Slack, and you can even meme yourself with Zoom backgrounds.
Compliance regulations are some of the most important guidelines your organization needs to meet.
AWS is one of the cloud computing providers that offers production-ready CI/CD services.
Last week, we explored the Amazon Web Services (AWS) suite of cost. Today, we’ll explore the usage of management tools that can help you take control of your AWS bill.
We learn from the RightScale (now Flexera) 2019 State of the Cloud Report that cloud adoption has become pretty much universal, and public cloud adoption is growing significantly.
If you think of the Amazon Web Services (AWS) cloud as just another infrastructure on which to run your web apps and services, then this blog post is for you.
In our previous post, we discussed the history of serverless, Platform as a Service (PaaS), Backend as a Service (BaaS), and Functions as a Service (FaaS).
Despite its name, serverless doesn’t mean servers are absent—that is impossible because code still needs to run somewhere.
This summer, Media Temple launched a dramatic change in our web presence. The design certainly looks different than 2018, and there’s a lot that’s working differently under the hood as well.
Now that we’ve discussed the serverless architecture and its use cases are clearer in the first part of our Serverless series, here’s a summary of some of its key benefits and challenges.
Serverless is an approach to software development that abstracts the server layer from the application code.
The less time an agency can spend explaining what it’s trying to do, the more time it can spend doing it.
If you are wondering which services you can use for deploying microservices on Amazon Web Services (AWS), check out the recommendations below. Amazon Elastic Container Service/AWS Fargate Microservices does not translate to containers.
After reviewing the pros and cons of monolithic and microservices architectures in part one of this series, it’s time to talk about whether or not you should switch to a microservices architecture.