Will my apps which I deployed on Heroku be available after the elimination of free tier/plans?
If yes, in addition to this, will I be able to build and make changes to the same applications?
If your apps are running on free dynos and you don't upgrade, and you aren't eligible as a student, they will not be available:
Starting November 28, 2022, free Heroku Dynos, free Heroku Postgres, and free Heroku Data for Redis® plans will no longer be available. If you have apps using any of these resources, you must upgrade to paid plans by this date to ensure your apps continue to run and retain your data. For students, we will announce a new program by the end of September. See our blog and FAQ for more info.
The referenced blog post contains a bit more info (emphasis added):
Starting October 26, 2022, we will begin deleting inactive accounts and associated storage for accounts that have been inactive for over a year. Starting November 28, 2022, we plan to stop offering free product plans and plan to start shutting down free dynos and data services. We will be sending out a series of email communications to affected users.
Related
I'm using Heroku's Pipeline feature to manage the stages of my application. I received an email about Heroku getting rid of their free plans, so I went ahead and upgraded my plan just now. Currently, I have one app with two database add-ons in Heroku. This is the first time that I've used their Pipeline feature—and I'm by no means a Heroku expert. I have two questions:
Do I need to purchase dynos for every new app that I use Heroku for? The plan that I ended up purchasing was the Production plan (since the app is for a client), and I also purchased two psql database add-ons which are attached to the app.
Since I'm using their pipeline for my one app, I have staging and prod versions of the app assigned to their appropriate branches in the repo. The prod app is where I upgraded to the paid plan. Do I need to purchase any dynos or add-ons for the staging app within the Pipeline? I was able to attach the databases with no issue, but I purchased a dyno for the staging app just to be safe.
Feel free to share any of your favorite Heroku alternatives as well—I'm only using Heroku because that's what I learned how to use in school.
Fellow Heroku user here!
Do I need to purchase dynos for every new app that I use Heroku for?
Yes. Heroku have basically said they’re getting rid of free plans for all applications due to wanting to make more money security reasons. So staging apps will also fall under this.
Basically, it sounds like there’s going to be no free tier dynos or first party add-ons from Heroku going forward. They do suggest for non-production apps (like testing and staging apps) to turn your dynos on when in use, and off when not in use, and you’ll only be billed for the time the dyno is on.
I‘m not sure which plan is the Production plan (I couldn’t see it on the pricing page) but maybe try out Hobby first. I have multiple apps running with paid Hobby-tier dynos and they have ran just fine without really spiking the CPU or memory available in those dynos. But I’m running PHP apps, so your milage may vary if you’re using another tech stack, or do get more load than my apps.
Recently I was informed that Heroku will be terminating their free dynos which offered 1000 hrs/month to users with a registered credit card. Users will have to upgrade to the $7/m Hobbyist plan on the minimum before the 28th of November 2022 to continue with the service.
With this offer gone I was curious to know what the StackOverflow community thinks is a viable alternative to Heroku?
For me Fly.io, render.com, Supabase (for postgres databses) just to name some alternatives. But Render would be the best choice in my opinion.
I cannot access my heidisql database because my google cloud trial version is over so I want to de-host my laravel app from google cloud platform and want to develop only on localhost.
When a free trial ends, you have 30 days to restore your resources by upgrading to a paid account; otherwise, the data and resources are not longer available anymore. You can take a look on the End of the free trial section of the Billing FAQs to know more about this matter.
What happens when my free trial ends?
After your trial ends, the resources you created during the trial are stopped, but can
be restored if you upgrade to a paid account within 30 days.
Within that 30-day period, you can also contact Google Billing Support
to export any data you stored in Google GCP services (other than on
Compute Engine). After 30 days, your data and resources are not
available, even if you upgrade.
Caution: Because there is no automated way to export data from Compute
Engine, you are responsible for exporting any data stored on Compute
Engine before your free trial ends.
As most developers know at this point, Parse is shutting down early 2017 but they have been pushing clients to migrate their services. I have a huge client who will be using Parse for Push Notifications in July and August and want to make sure that Parse will still be functioning 100%. I understand them wanting people to migrate, but they don't seem clear on whether their services will be interrupted.
They have been very clear about it :
Why are you using Parse when they are going to shut down & want you to adopt mongoDb? If you have an app there with mongo your app would work fine, but why not go with other options?
Refer : Parse Migration
Also read : My app relies on parse, I have no backend skills
Parse.com will be fully functional until the shutdown on January 28, 2017 although with weaker performance after April 28th.
According to members of the Parse team:
Hi there, I'm part of the team who is actively helping people migrate
their apps. The answer is that we don't know how this may affect push
notifications.
When we announced that the hosted Parse service will be shut down next
January, we also provided a migration guide where we have shared a
recommended set of guidelines for your migration:
Migrate your database by April 28th, 2016 Migrate your API traffic by
July 28th, 2016 We are committed to maintaining the Parse API up and
running until January of next year, but we highly recommend starting
your migration work as soon as possible. We are focusing our efforts
on people who are following our recommended instructions.
Source
and
If you have migrated your database to your own MongoDB, you will be
fine, your apps will receive full priority. If you haven't migrated
your database, you app will keep working, but requests might take
longer or have a higher failure rate.
Source
I want to set up a Windows Azure account.
I'm an MSDN Subscriber so I get it for "free" the first 16 months.
Still, Microsoft want my credit card number just in case I go over the free limit.
In theory, this means I'm writing a carte blanche to MS to bill my credit card.
I want to know if anyone has been using Azure and if there's anyway of setting it to simply stop working if it gets near the cap where it would start to cost me something??
Today, there are no usage caps you can place on your account. Regarding the credit card and carte blanche ability to bill you: you'd only be billed for overage beyond the "free" stuff. Microsoft recently instituted an email-alert feature that lets you know when you've used 75% of your available resources. I believe that went live a few weeks ago.
Simply put: you get 750 compute-hours monthly (metered on a 1-hour boundary). This gives you enough hours to run a single, small instance 24x7, as there are just under 750 hours in a month. If you leave two instances running full-time, you'll go over your allotment and be charged.
If you're just learning, the MSDN account is fantastic. Just remember to delete your deployment at the end of the day (or when you're done trying something out), instead of letting it run 24x7. With a bit of prudence, you'll easily be able to test multi-instance applications and avoid ever being charged.
You can also log into the billing portal from the Azure portal. This shows a very detailed breakdown of your monthly usage, and with a quick scan you'll see how you're doing regarding compute-hours.
I keep mentioning compute-hours but not storage or bandwidth. Unless you're doing some extreme development, I doubt you'll run into any storage or bandwidth overruns. Same goes for SQL Azure - stick with Web Edition databases (and only 3 databases) and you'll have no issue there.
I wrote two blog posts that might also be helpful when thinking about how to manage cost so you don't get charged:
The True Cost of Web and Worker Roles
Staging and Compute-Hour Metering
In addition to David's answer, I would also suggest maximizing your use of the local Azure runtime that comes with the SDK. You can create web & worker roles and blobs/tables/queues. Iterate there until you are happy with how everything works - then publish to the public cloud.
There is no charge for the SDK or the local runtime.
The December 2011 release of Windows Azure introduced a much revamped billing portal which, amongst other things, introduced the ability to cap spend on introductionary accounts and MSDN accounts.
Whilst you still need to provide credit card for your MSDN Account, all accounts are automatically created with spending limit of $0; a limit one can remove from the billing portal.
See - http://www.brianhprince.com/post/2011/12/20/New-Sign-Up-for-Windows-Azure-and-Spending-Caps.aspx