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
LinkPoint Connect
Score 9.0 out of 10
N/A
LinkPoint Connect promises to streamline data entry and access by enabling users to instantly view CRM data within their email client. This sales intelligence solution integrates Salesforce and Microsoft Dynamics CRM data in Outlook or IBM Notes. According to the vendor, key capabilities include: View real-time Salesforce data without ever leaving your email. Click on an email, and the LinkPoint Connect Side Panel instantly displays that contact’s information directly from…
$192
per user, per year
Pricing
AWS Elastic Beanstalk
LinkPoint Connect
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
LinkPoint Connect for Outlook + Salesforce
$192
per user, per year
LinkPoint Connect for Outlook + Microsoft Dynamics CRM
$192
per user, per year
LinkPoint Connect for IBM Notes + Salesforce
$228
per user, per year
LinkPoint Connect for IBM Notes + Microsoft Dynamics CRM
$228
per user, per year
Offerings
Pricing Offerings
AWS Elastic Beanstalk
LinkPoint Connect
Free Trial
No
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
$16 per user per year
Additional Details
—
Subscriptions are billed annually. Discounts available for non-profits. Volume discounts available. LinkPoint Connect Solutions are available for Outlook and IBM Notes users. These include preconfigured implementations for Advologix, Apto, Apttus, FinancialForce.com, Jobscience, Navatar, Pardot, Salesforce Shield, and TaskRay.
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.
LinkPoint is well suited to any situation where Outlook is used for email correspondence and calendar items and there is need to have a record of those items and/or perform connected actions (schedule tasks, follow up reminders, etc.) in Salesforce. Automating this process and removing as much duplication of work as possible is the primary goal and the primary benefit that LinkPoint provides. In addition to efficiency, automating the process also provides a pretty substantial increase in accuracy, removing ca. 50% of the chance for human error. It's pretty simple functionality in concept, but extremely valuable in execution.
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.
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.
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.
It is a great tool to manage your applications. You just need to write the codes, and after that with one click, your app will be online and accessible from the internet. That is a huge help for people who do not know about infrastructure or do not want to spend money on maintaining infrastructure.
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.
- 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.
Prior to our move to LinkPoint, we used the Salesforce add-in for Outlook. This required manual syncing of email and calendar items and no easy to use interface between the two programs. It was very cumbersome for me to use, to the point where I quit using it altogether some time ago. I found it far less frustrating to just switch back and forth between Outlook and Salesforce and manually perform the requisite actions, create tasks or other items, enter the required data, etc.