The Adobe Experience Platform is a platform-as-a-service (PaaS) serving as the foundation of the Adobe Experience Cloud, and is provided as a customer experience management platform with real-time customer profiles, continuous intelligence, and an open and extensible architecture that enables delivering personalized experiences at scale.
N/A
AWS Elastic Beanstalk
Score 8.0 out of 10
N/A
AWS Elastic Beanstalk is the platform-as-a-service offering provided by Amazon and designed to leverage AWS services such as Amazon Elastic Cloud Compute (Amazon EC2), Amazon Simple Storage Service (Amazon S3).
$35
per month
Twilio Segment
Score 8.3 out of 10
N/A
Segment is a customer data platform that helps engineering teams at companies like Tradesy, TIME, Inc., Gap, Lending Tree, PayPal, and Fender, etc., achieve time and cost savings on their data infrastructure, which was acquired by Twilio November 2020. The vendor says they also enable Product, BI, and Marketing teams to access 200+ tools (Mixpanel, Salesforce, Marketo, Redshift, etc.) to better understand and optimize customer preferences for growth— all integrations are pre-built and…
$120
per month
Pricing
Adobe Experience Platform
AWS Elastic Beanstalk
Twilio Segment
Editions & Modules
No answers on this topic
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Free
$0.00
Includes 1,000 visitors/mo
Team
$120.00
Includes 10,000 visitors/mo
Business
Contact Sales
Custom Volume
Offerings
Pricing Offerings
Adobe Experience Platform
AWS Elastic Beanstalk
Twilio Segment
Free Trial
No
No
Yes
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Adobe Experience Platform
AWS Elastic Beanstalk
Twilio Segment
Considered Multiple Products
Adobe Experience Platform
Verified User
Analyst
Chose Adobe Experience Platform
We are more integrated with other Adobe products and so it was an easy decision
The Adobe Experience Platform is well suited for companies that are maturing or have matured in their digital offerings and are looking for very sophisticated tools to elevate to the next level. It's also for well resourced teams, both financially and head count to take advantage of the deep functionality and integrations.
I have been using AWS Elastic Beanstalk for more than 5 years, and it has made our life so easy and hassle-free. Here are some scenarios where it excels -
I have been using different AWS services like EC2, S3, Cloudfront, Serverless, etc. And Elastic Beanstalk makes our lives easier by tieing each service together and making the deployment a smooth process.
N number of integrations with different CI/CD pipelines make this most engineer's favourite service.
Scalability & Security comes with the service, which makes it the absolute perfect product for your business.
Personally, I haven't found any situations where it's not appropriate for the use cases it can be used. The pricing is also very cost-effective.
Best suited: - Merging emails coming from: Facebook leads forms, Unbounce or landing pages forms, Google forms, any other kind of lead generation tool and bundling all that information together for a single user "profile". - Passing events generated in multiple applications by the same user (product selected in web, product discarded in cart, etc) and delivering those events into other applications (like a CRM) Less appropriate: - Reading/updating data directly from segment from a frontend application
Getting a project set up using the console or CLI is easy compared to other [computing] platforms.
AWS Elastic Beanstalk supports a variety of programming languages so teams can experiment with different frameworks but still use the same compute platform for rapid prototyping.
Common application architectures can be referenced as patterns during project [setup].
Multiple environments can be deployed for an application giving more flexibility for experimentation.
Multi-platform. Segment has easy integrations in many different web, backend, and app platforms/frameworks. We use the Segment SDK in Android and iOS as well as our node.js backend.
Segment is fairly affordable for early-stage companies that are trying out different analytics software. The "developer" plan is free and is suitable for most companies with products that have a small user base.
The UI is great! It is extremely intuitive and easy-to-learn, and this made it take very little time to integrate this software into our analytics and marketing workflows.
Limited to the frameworks and configurations that AWS supports. There is no native way to use Elastic Beanstalk to deploy a Go application behind Nginx, for example.
It's not always clear what's changed on an underlying system when AWS updates an EB stack; the new version is announced, but AWS does not say what specifically changed in the underlying configuration. This can have unintended consequences and result in additional work in order to figure out what changes were made.
More and richer sources. For example, MailChimp is a source but the data you get from MailChimp is quite limited. I ended up writing my own scripts to take better advantage of MailChimp's API because Segment's integration was lacking.
Better examples on how to set up event tracking. Pageview tracking is easy enough, but it would be nice if they had a sample app and corresponding code for it and showed you, via Git commits, how to add various kinds of events.
As our technology grows, it makes more sense to individually provision each server rather than have it done via beanstalk. There are several reasons to do so, which I cannot explain without further diving into the architecture itself, but I can tell you this. With automation, you also loose the flexibility to morph the system for your specific needs. So if you expect that in future you need more customization to your deployment process, then there is a good chance that you might try to do things individually rather than use an automation like beanstalk.
Overall I really like the Adobe Experience Cloud after a couple years of figuring out various tools. They are extremely powerful. The time commitment to learn them is high since it's not a tool you can easily begin using without much training.
The overall usability is good enough, as far as the scaling, interactive UI and logging system is concerned, could do a lot better when it comes to the efficiency, in case of complicated node logics and complicated node architectures. It can have better software compatibility and can try to support collaboration with more softwares
Adobe has support at all levels and for each product but beyond tool questions you'll often be told they can help but it requires some paid consulting hours. So you either hire Adobe consultants or find 3rd part consultants who know their products well.
As I described earlier it has been really cost effective and really easy for fellow developers who don't want to waste weeks and weeks into learning and manually deploying stuff which basically takes month to create and go live with the Minimal viable product (MVP). With AWS Beanstalk within a week a developer can go live with the Minimal viable product easily.
Over the period it took us to set up, we kept going back to their enablement team to help us with the setup, and they were always ready and were very helpful in the entire process. Even with their documentation, they took the time out to help us work through the process. We've never had a message/email unanswered for more than an hour on working days.
- Do as many experiments as you can before you commit on using beanstalk or other AWS features. - Keep future state in mind. Think through what comes next, and if that is technically possible to do so. - Always factor in cost in terms of scaling. - We learned a valuable lesson when we wanted to go multi-region, because then we realized many things needs to change in code. So if you plan on using this a lot, factor multiple regions.
We also use Heroku and it is a great platform for smaller projects and light Node.js services, but we have found that in terms of cost, the Elastic Beanstalk option is more affordable for the projects that we undertake. The fact that it sits inside of the greater AWS Cloud offering also compels us to use it, since integration is simpler. We have also evaluated Microsoft Azure and gave up trying to get an extremely basic implementation up and running after a few days of struggling with its mediocre user interface and constant issues with documentation being outdated. The authentication model is also badly broken and trying to manage resources is a pain. One cannot compare Azure with anything that Amazon has created in the cloud space since Azure really isn't a mature platform and we are always left wanting when we have to interface with it.
We chose Twilio Segment for the good API integration and node resources, I would use Ontraport again, particularly if I didn't have the requirements for API and development/platform integration. Certainly the set up and management is easy and seamless with both the API and the user interface to use depending on circumstances and requirements.
Segment has enabled us to get a full view of our front end activity, join it to our back-end activity, and get full visibility into our funnels and user activity.
Segment lets us send events to ad tools with a full audit trail so all the numbers line up.
Segment also brings data from other sources into our data warehouse, saving our data engineering time from building commodity connectors.
