DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Join us tomorrow at 1 PM EST: "3-Step Approach to Comprehensive Runtime Application Security"
Save your seat
  1. DZone
  2. Data Engineering
  3. Big Data
  4. Serverless Architectures on AWS

Serverless Architectures on AWS

Serverless is made for event-driven architectures. Dividing your app into functions and making use of microservices architecture are keys to success in the cloud.

Andreas Wittig user avatar by
Andreas Wittig
·
Mar. 02, 17 · Opinion
Like (2)
Save
Tweet
Share
9.13K Views

Join the DZone community and get the full member experience.

Join For Free

This article is featured in the new DZone Guide to the Cloud: Native Development and Deployment. Get your free copy for more insightful articles, industry statistics, and more!

A serverless platform allows you to run your application—including computing, storing, and networking —without the need for spinning up and managing a single (virtual) machine. This article focuses on serverless architectures on AWS including Lambda, API Gateway, DynamoDB, S3, and more. The architecture patterns can be transferred to other cloud platforms as well.

Being able to focus on software development instead of operating a fleet of servers is the primary driver behind serverless. Alternatively, as Werner Vogels, CTO of Amazon.com, says: “No server is easier to manage than no server.” Another important aspect of serverless infrastructure is finely granular billing and extreme scalability. To give you an impression of typical use cases, here are some serverless applications I have been working on recently:

  • Collecting metrics from web application with a REST API in a high load scenario.
  • Extracting and storing data from incoming emails containing order and status information.
  • Creating a REST API providing a standard CRUD backend.
  • Collecting and transforming data within an ETL process in a big data scenario.
  • Analyzing log messages from a real-time data stream.
  • Building a chatbot that is interacting with multiple APIs in the background.

Limitations

The ability to execute source code on a highly available and scalable infrastructure is the heart of every serverless platform. AWS Lambda, for example, allows you to run your source code in response to events. AWS provides the computing infrastructure and a runtime environment for JavaScript (Node.js), Java, Python, or .NET Core (C#). A typical serverless application consists of multiple functions. On AWS Lambda, there is an execution timeout of 5 minutes for every function execution. Nevertheless, you can execute the same or different functions in a highly parallel manner.

Dividing your application into small functions is necessary when following a serverless approach. Making use of microservice architectures helps you to achieve that goal. Serverless is made for event-driven architectures. An event is a source for triggering a serverless function and the glue when orchestrating multiple serverless functions forming a system.

Triggering a function with AWS Lambda is possible based on the following events:

  • Incoming HTTPS request.
  • Changing data stored in a database or object storage.
  • Incoming message (e.g. email).
  • Publishing a task to a topic or real-time data stream.
  • Scheduled event (comparable with a cronjob).

Read the rest of this article and a lot more in:Cloud Guide

DZone's Guide to the Cloud: Native Development and Deployment

Including:

  • Industry Research Data
  • Articles Written by Industry Experts
  • Cloud Architecture Infographic
  • Directory of the Best Tools & Solutions
Free Download

AWS Architecture Big data Web application

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Load Balancing Pattern
  • OpenID Connect Flows
  • Distributed SQL: An Alternative to Database Sharding
  • Web Application Architecture: The Latest Guide

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: