Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monetize with Pro version #894

Open
tj opened this Issue Jul 17, 2018 · 9 comments

Comments

Projects
None yet
6 participants
@tj
Copy link
Member

tj commented Jul 17, 2018

Thumbs up if you/your company would be interested in a more robust monthly subscription pro version. This would let me focus on the project again, at the moment I can't even really review contributions since they shouldn't be blindly merged without QA.

I'd also like to get rid of the Terraform dependency since it has a pretty large learning curve and doesn't integrate naturally with the project, so Apex would likely have its own more user-friendly CloudFormation integration, similar to Up's.

In the 2.0 version it should be much easier to define scheduled events (cron jobs), queues, pub/sub, and other resources in a declarative manner without deep knowledge of how IAM policies work. Among other things like local testing, possibly a UI for monitoring and logs, encrypted env vars etc.

I'd love to hear any pain-points you're running into or features you'd like to see as well.

@tj tj added the feedback wanted label Jul 17, 2018

@tj tj changed the title Monetize Monetize with Pro version Jul 17, 2018

@maxbeatty

This comment has been minimized.

Copy link

maxbeatty commented Jul 17, 2018

fwiw we've really enjoyed the terraform integration. only ask would be for more support for flags like plan -out. modules can go a long way in reducing learning curve.

excited to see apex getting some ❤️

@tj

This comment has been minimized.

Copy link
Member Author

tj commented Jul 17, 2018

I wish it was embeddable, that's my main complaint, the learning curve is a little awkward when you have to go learn another tool haha. It's still nicer than CloudFormation in quite a few ways though, tough calllll.

Does your team use TF for other stuff as well (EC2 etc) or mostly serverless?

@drinkmorewaters

This comment has been minimized.

Copy link

drinkmorewaters commented Jul 19, 2018

Get rid of Terraform as it's not the core sales product and if you don't want to work with it, it's your product! Package everything into a dashboard and CLI similar to now.sh or Apex Ping so that it's more approachable for 'everyone'. I'd suggest converging all products into one dashboard, similar to Cloudflare, AWS, Google Cloud. Converging products means you're not maintaining two seperate front end bases. Offer free, paid and enterprise plans. Or offer a 'Pro' version with a monthly subscription.

Either way, do what YOU believe is best as you believed Express, Koa, Apex was best. I'm pretty sure we trust your decision at this point :D

@ngallardo

This comment has been minimized.

Copy link

ngallardo commented Aug 16, 2018

Really excited to hear this news. Up has been an awesome step forward from Apex. We currently use both extensively and matching semantics across both would relieve a lot of context switching when we go between the two tools.

+1 to removing Terraform. We only use it for serverless stuff and manage that separately from Apex/Up.

I'd pay for a pro version even if it only added these two features:

  • Encrypted env vars the way they're done with Up.

  • Making the semantics of stages work the same way they do in Up. It can get a little confusing keeping straight that "env" is "stage", and that "env" is something different in Up. Don't know if this means scrapping the "alias" and making that the "stage".

I'd consider it a bonus if I could:

  • Specify simple triggers (CloudWatch Events, SNS, SQS, maybe Kinesis), and could do so by stage or alias.

  • Run functions locally in a development stage. We can trigger them today via unit / integration test framework. Was thinking of something that would simulate Lambda execution locally (maybe with sample trigger payloads - https://docs.aws.amazon.com/lambda/latest/dg/eventsources.html). This is likely beyond the scope of Apex but maybe a useful compliment. Happy to contribute to a project that bootstraps this.

Maybe a stupid question but, are you thinking of matching the default build commands to install requirements like in Up? I'm all for that with the ability to continue overriding via hooks as well.

@tj

This comment has been minimized.

Copy link
Member Author

tj commented Aug 16, 2018

@ngallardo thanks for the feedback!

The thing we decided to work on fits the same niche, but it's quite a bit more ambitious so we might give it a new name and its own website etc. It'll definitely support all the major integrations out of the box (SQS, Kinesis and friends).

Stage-wise it'll be closer to what Up has, I definitely want to make sure it's flexible enough for people to spin up per-team or per-dev environments for testing since local testing with all these AWS services is almost impossible.

The CLI portion might end up being really similar to Up, I'll definitely try to keep the semantics similar there.

@vespertilian

This comment has been minimized.

Copy link

vespertilian commented Aug 30, 2018

I am using Apex and Apex UP. It would be nice for me if there was a combined pro plan, if you end up adding a paid version.

It would also be nice if I could have one single binary option for both Apex Up and Apex that ties together the stages etc for deployment of all the things.

My specific use case is Apex Up for deployment of GraphQL API and Apex for a SNS topic that triggers SES outside of the VPC firewall. SNS is a private link function.

Like @ngallardo suggested if Apex could make triggering easier, and linking that would help my situation. I currently link with a custom node script.

This feature would be useful for anyone who uses a DB inside their VPC and wants to bust out of it via SNS to access outside services.

@tj

This comment has been minimized.

Copy link
Member Author

tj commented Aug 30, 2018

@vespertilian I think you'll be interested in this next project as well :D I'll let you guys know once we have it in some kind of beta. It's different enough that I don't want to call it Apex 2.0, so I might still revisit making Apex nicer at some point.

@vespertilian

This comment has been minimized.

Copy link

vespertilian commented Aug 31, 2018

@tj Excited to find out more!

@j

This comment has been minimized.

Copy link

j commented Nov 9, 2018

We'd definitely be on this.

Our current lambda setup is:

  • GraphQL HTTP
  • SNS Publishers (email, chromium, etc) - HTTP event
  • SNS Consumers (email subscription, transactional emails, chromium snapshots) - SNS event

I'd LOVEEEE to get away from Serverless and use Apex/Up only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.