Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs Apache Flink: What are the differences?
Differences between AWS Lambda and Apache Flink
Execution Model: AWS Lambda follows an event-driven execution model, where functions are triggered by events and run in short-lived containers. On the other hand, Apache Flink follows a stream processing model, where data is processed continuously in real-time or batch mode.
Data Processing: AWS Lambda is primarily designed for running small, stateless functions in response to events. It is well-suited for simple data transformations or event-driven tasks. In contrast, Apache Flink is a powerful distributed stream processing framework that can handle large-scale data streams and complex processing workflows.
Scalability: AWS Lambda provides automatic scaling, allowing functions to dynamically scale based on the incoming workload. It can handle bursts of traffic and scale down when not in use. Apache Flink, being a distributed processing framework, inherently provides scalability by allowing the parallel execution of tasks across nodes in a cluster.
State Management: AWS Lambda is stateless by design and does not provide built-in storage for maintaining state between function invocations. It relies on external storage services like AWS DynamoDB or S3. In contrast, Apache Flink offers built-in support for managing state, allowing for efficient processing of stateful computations such as maintaining user sessions or aggregating values over time.
Batch Processing vs. Stream Processing: AWS Lambda is primarily focused on executing functions in response to events, which is suitable for real-time or near real-time processing. Apache Flink, on the other hand, can handle both batch and stream processing workloads, allowing for the efficient processing of large volumes of data in both real-time and offline scenarios.
Ecosystem and Integrations: AWS Lambda integrates seamlessly with other AWS services and offers a wide range of event sources, making it easy to build serverless applications within the AWS ecosystem. Apache Flink, being a general-purpose stream processing framework, can integrate with various data sources and systems, including Apache Kafka, Hadoop, and more, providing flexibility in data integration.
In Summary, AWS Lambda is an event-driven execution service suitable for small, stateless functions, while Apache Flink is a distributed stream processing framework designed for handling large-scale data processing and supporting both batch and stream processing workflows.
Need advice on what platform, systems and tools to use.
Evaluating whether to start a new digital business for which we will need to build a website that handles all traffic. Website only right now. May add smartphone apps later. No desktop app will ever be added. Website to serve various countries and languages. B2B and B2C type customers. Need to handle heavy traffic, be low cost, and scale well.
We are open to either build it on AWS or on Microsoft Azure.
Apologies if I'm leaving out some info. My first post. :) Thanks in advance!
I recommend this : -Spring reactive for back end : the fact it's reactive (async) it consumes half of the resources that a sync platform needs (so less CPU -> less money). -Angular : Web Front end ; it's gives you the possibility to use PWA which is a cheap replacement for a mobile app (but more less popular). -Docker images. -Kubernetes to orchestrate all the containers. -I Use Jenkins / blueocean, ansible for my CI/CD (with Github of course) -AWS of course : u can run a K8S cluster there, make it multi AZ (availability zones) to be highly available, use a load balancer and an auto scaler and ur good to go. -You can store data by taking any managed DB or u can deploy ur own (cheap but risky).
You pay less money, but u need some technical 2 - 3 guys to make that done.
Good luck
My advice will be Front end: React Backend: Language: Java, Kotlin. Database: SQL: Postgres, MySQL, Aurora NOSQL: Mongo db. Caching: Redis. Public : Spring Webflux for async public facing operation. Admin api: Spring boot, Hibrernate, Rest API. Build Container image. Kuberenetes: AWS EKS, AWS ECS, Google GKE. Use Jenkins for CI/CD pipeline. Buddy works is good for AWS. Static content: Host on AWS S3 bucket, Use Cloudfront or Cloudflare as CDN.
Serverless Solution: Api gateway Lambda, Serveless Aurora (SQL). AWS S3 bucket.
We have a Kafka topic having events of type A and type B. We need to perform an inner join on both type of events using some common field (primary-key). The joined events to be inserted in Elasticsearch.
In usual cases, type A and type B events (with same key) observed to be close upto 15 minutes. But in some cases they may be far from each other, lets say 6 hours. Sometimes event of either of the types never come.
In all cases, we should be able to find joined events instantly after they are joined and not-joined events within 15 minutes.
The first solution that came to me is to use upsert to update ElasticSearch:
- Use the primary-key as ES document id
- Upsert the records to ES as soon as you receive them. As you are using upsert, the 2nd record of the same primary-key will not overwrite the 1st one, but will be merged with it.
Cons: The load on ES will be higher, due to upsert.
To use Flink:
- Create a KeyedDataStream by the primary-key
- In the ProcessFunction, save the first record in a State. At the same time, create a Timer for 15 minutes in the future
- When the 2nd record comes, read the 1st record from the State, merge those two, and send out the result, and clear the State and the Timer if it has not fired
- When the Timer fires, read the 1st record from the State and send out as the output record.
- Have a 2nd Timer of 6 hours (or more) if you are not using Windowing to clean up the State
Pro: if you have already having Flink ingesting this stream. Otherwise, I would just go with the 1st solution.
Please refer "Structured Streaming" feature of Spark. Refer "Stream - Stream Join" at https://spark.apache.org/docs/latest/structured-streaming-programming-guide.html#stream-stream-joins . In short you need to specify "Define watermark delays on both inputs" and "Define a constraint on time across the two inputs"
When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:
- Developer Experience trumps everything.
- AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
- If you need geographic spread, AWS is lonely at the top.
Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:
- Pure, uncut, self hosted Kubernetes — way too much complexity
- Managed Kubernetes in various flavors — still too much complexity
- Zeit — Maybe, but no Docker support
- Elastic Beanstalk — Maybe, bit old but does the job
- Heroku
- Lambda
It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?
I chopped that question up into the following categories:
- Developer Experience / DX 🤓
- Ops Experience / OX 🐂 (?)
- Cost 💵
- Lock in 🔐
Read the full post linked below for all details
Pros of AWS Lambda
- No infrastructure129
- Cheap83
- Quick70
- Stateless59
- No deploy, no server, great sleep47
- AWS Lambda went down taking many sites with it12
- Event Driven Governance6
- Extensive API6
- Auto scale and cost effective6
- Easy to deploy6
- VPC Support5
- Integrated with various AWS services3
Pros of Apache Flink
- Unified batch and stream processing16
- Easy to use streaming apis8
- Out-of-the box connector to kinesis,s3,hdfs8
- Open Source4
- Low latency2
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Lambda
- Cant execute ruby or go7
- Compute time limited3
- Can't execute PHP w/o significant effort1
Cons of Apache Flink
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is Apache Flink?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Apache Flink?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Lambda?
What tools integrate with Apache Flink?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+6
+4
+7
+8
+47
+43
+26
+23