It's better to run code IN AWS than to run it ON AWS
Massimo Re Ferrè, Director, Product Management at Amazon Web Services (AWS)

It's better to run code IN AWS than to run it ON AWS

This concept is central to our philosophy and our embracing of cloud-native, serverless systems, and a key enabler of our software-development-as-a-service model. It's a subtle concept that sometimes requires diving a bit into the technology to understand.

To build a system ON AWS you are writing applications in a traditional way, using frameworks and dependencies, and building deployable artifacts and containers. You are using AWS (or any public cloud provider) for compute, networking, and other commodity resources (DNS, caching, databases, etc.).

To build a system IN AWS you are taking advantage of business applications and services managed and maintained by AWS into which you construct and deploy business logic.

So why is building IN AWS better? A lot of reasons, but a few of my favorites:

  • It's operationally efficient, I.e. a very high mean time to maintenance (see attached article). That means it costs less to operate and maintain.
  • It's natively observable, meaning we can very easily monitor and respond to performance metrics - both business and technical.
  • It costs less to build and maintain. You're simply writing less code and you're letting AWS handle non-core domain functionality.
  • It's understandable. You can look at Step Functions and see exactly how the logic works. And you can use the system to document the system.

When you build your system IN AWS you are taking advantage of the full power of the platform. You are positioned well to leverage new services as they come out. AWS manages almost all of your technology stack for you. And the pricing is on-demand, able to grow (and if needed contract) with your business.

What do you think? Comment here, or better, give me a shout and let's discuss.

Eric Hochhalter

Creative Technologist | Software Product Designer & Architect | Certified AWS Cloud Consultant | Domain Driven Design Practitioner

6 个月

I love how building software *IN* AWS serverless services means there's just less code, and therefore less friction. Combine that with the visual low-code nature of Step Functions, and it becomes easier to understand for everybody. Low friction and high understanding is the way to go. Smooth is Fast!

Dave Raring

Technology Executive | Builder | Entrepreneur

6 个月

Absolutely! When we build in AWS, we're all about focusing on what matters first: the business. Because we have made large investments in standardizing our approach to Infrastructure as Code (IaC), we're able to make the most of AWS's features while ensuring that our applications meet not only our customers' money-making needs but also their regulatory and security requirements - ie all the back office stuff that usually gets de-priorityzed. So, unlike agnostic software applications where you often end up adding extra code just to get the basics in place, AWS's managed services coupled with a comprehensive IaC methodology, let us hit the ground running. It's all about speeding up development, staying secure, and giving our customers the best possible solutions.

要查看或添加评论,请登录

社区洞察

其他会员也浏览了