Heroku Blog

One of the goals of Ruby 3 is to have a 3x improvement in performance. If you're interested in how Ruby is planning to improve performance, this is a good read: https://blog.heroku.com/ruby-3-by-3

Disclosure: I work for Heroku. Heroku launched a cheaper managed Kafka 1.5 months ago. It starts at $100/month (pro-rated to second). That's ~$3.33/day. Great if you want to play, learn, or test out a proof-of-concept. It's multi-tenant, but interaction is nearly identical to interacting with a dedicated kafka cluster -- i.e. you can use any regular kafka client library. Check out docs[1] and launch blog post[2]. Happy to answer any questions here or through email (contact info in profile). [1]: https://devcenter.heroku.com/articles/multi-tenant-kafka-on-heroku [2]: https://blog.heroku.com/kafka-on-heroku-new-plans

I had asked a similar question on Quora [1] few years back. Here is the summary: - Facebook: https://www.facebook.com/Engineering?sk=notes - Google: http://google-engtools.blogspot.com/ - Twitter: http://engineering.twitter.com/ - Linkedin: http://engineering.linkedin.com/blog - Dropbox: https://tech.dropbox.com/ - Instagram: http://instagram-engineering.tumblr.com/ - Netflix: http://techblog.netflix.com/ - Flickr: http://code.flickr.com - Etsy: http://codeascraft.etsy.com/ - Yelp: http://engineeringblog.yelp.com/ - Heroku: https://blog.heroku.com/ - Airbnb: http://nerds.airbnb.com/ - Bitly: http://word.bitly.com/ - Evernote: https://blog.evernote.com/tech/ - Highscalability: http://highscalability.com/ [1] https://www.quora.com/What-are-the-companies-that-have-some-of-the-bes…

Indeed, it seems Elixir is one part complementary to Ruby and the other a great replacement whilst also keeping the main tenets of Ruby in-place. The only issue so far is that the libraries ecosystem is indeed quite young but that is natural. Still, Ruby (even without Rails) is at the moment a more productive environment. I really hope Ruby "3x3" [0] will be released soon enough and projects like Hanami [1] become production ready so that it can coexist in a complementary way rather than becoming replaceable. [0] - https://blog.heroku.com/ruby-3-by-3 [1] - http://hanamirb.org

Relevant: Ruby 3x3: Matz, Koichi, and Tenderlove on the future of Ruby Performance https://blog.heroku.com/ruby-3-by-3/

Ruby 3x3 is a plan to make Ruby 3 times faster than Ruby 2.x. Here's some further reading: http://engineering.appfolio.com/appfolio-engineering/2015/11/18/ruby-3… https://blog.heroku.com/where_will_ruby_go_now_talking_with_tenderlove… https://www.reddit.com/r/ruby/comments/3tje5a/ruby_3x3_ruby_3_will_be_…

Great that Heroku sponsored upsert and have support for 9.5 right now (in beta): https://blog.heroku.com/archives/2016/1/7/postgres-95-now-available-on…

Bit of a shameless plug, but we just announced official support yesterday on Heroku (https://blog.heroku.com/archives/2015/7/7/go_support_now_official_on_h… graduating from our community supported buildpack. We allow you to pick pretty freely which databases and other services you want to you use from our add-ons. We also have a free tier. Finally if you do give it a try would love to hear any feedback you have.

There is definitely great PHP support at Heroku: https://blog.heroku.com/archives/2014/4/29/introducing_the_new_php_on_…

yeah you're missing something, unless you're just running something low priority like a personal blog: Although an app may not require the resources of more than a single dyno, we recommend running at least 2 dynos for a production app. One reason for this is that dynos restart roughly every 24 hours, and dyno redundancy helps ensure that you don't experience excessive queueing or dropped requests while a single dyno restarts. Additionally, dynos and the processes running on them can occasionally crash, and having another dyno helps ensure that you don't have downtime while that dyno recovers. Finally, single web dynos sleep after an hour of inactivity, and having a second dyno means that all dynos will stay awake.[1] [1] https://blog.heroku.com/archives/2013/4/26/introducing_production_chec…

I think that overstates it a bit, but yes, there are problems with Unicorn and slow clients. We're investigating: https://blog.heroku.com/archives/2013/4/3/routing_and_web_performance_… If this is an immediate problem for you, it might be worth your while to make your app threadsafe, which gives you more concurrent webserver options.

I've posted an update on our blog, with another to follow tomorrow: https://blog.heroku.com/archives/2013/2/15/bamboo_routing_performance/

Heroku's response: Hi Steve, I've been reading through all the concerns from customers, and I want every single customer to feel that Heroku is transparent and responsive. Our job at Heroku is to make you successful. Getting to the bottom of this situation and giving you a clear and transparent understanding of what we’re going to do to make it right is our top priority. I am committing to the community to provide more information as soon as possible, including a blog post on http://blog.heroku.com. Oren Teich Heroku GM

>> I am committing to the community to provide more information as soon as possible, including a blog post on http://blog.heroku.com > What's the point of posting a link to the front page of your blog, where the most recent article is 15 days old (4 hours after the comment above)? I think OP is saying 'I am going to investigate the situation; when I am finished here [the blog] is where I will post my response', not that there is something there already. That said, it's all a little too PR-Bot for my taste (although there's probably only so many ways to say the same info without accidentally accepting liability or something).

My problem with this type of thinking is that is too easy for Y to swoop in and take over X for you. They have the team, reputation, and recent success. You, most likely, have nothing. Examples: "We are facebook for bicycles!": that's just a facebook group. "We are Heroku for PHP/Clojure/Python":http://blog.heroku.com/archives/2011/8/3/polyglot_platform/ These are my best examples, but if X is just a feature that Y could implement or acquire, then making that comparison could be a major mistake. If they expand into your niche, then your X of Y idea backfires on you hardcore. Edit: I saw that my variables were reversed at some places.

Heroku just released some major updates to their Postgres offering as well. See the blog for info: http://blog.heroku.com/

I started hosting a project on heroku recently and it is simply fantastic. They offer a free hosting with 5 MB of DB storage and they just changed their pricing scheme and offer a plan with 20Gb of DB storage for only $15/month. Definitely worth checking out. http://blog.heroku.com/archives/2010/1/21/pricing_changes_part_i/

API Gateway is the definite gotcha with serverless architectures. Whenever someone tells me how cheaper serverless is, I figure they haven't actually dived in to see how many AWS resources besides Lambda are required for a production deployment. It is convenient in several use cases, but for an endpoint or even an entire API that is going to receive a lot of load, managing servers is the more economical approach. If you need to get a one-off endpoint built that won't receive any significant amount of load, I think a serverless solution is great. But I wouldn't use it as my primary API architecture. Like most things in tech, there's no silver bullet. Context matters, and the best approach depends on many factors. I still recall this article by the creator of ipify on how he's able to receive upwards of 30 billion requests per month on Heroku for a fraction of the cost of API gateway: https://blog.heroku.com/scaling-ipify-to-30-billion-and-beyond

I'm the Java Languages Owner at Heroku. While I can't reveal in full detail why we do (or do not) officially support a particular language, I can say that it has nothing to do with how resource-hungry the runtime is :) Our determination to officially support a language is based on numerous factors including community demand, relationship with other technologies, suitability to the platform (C++ is really popular but not for web apps), and more. In any case, I wouldn't read too much into our support--it's not a determination on the language itself. Fun fact: Clojure was the first JVM language supported on Heroku back in 2011 (even before Java itself)! https://blog.heroku.com/clojure_on_heroku Today, Heroku support Java (with Maven or Gradle), Scala, and Clojure buildpacks. JRuby is supported via the Ruby buildpack. Buildpacks are the mechanism that prepares each app for production, so in some ways our support is more tightly coupled to the build tools than the language. That's why we don't have a Kotlin buildpack (it can use the Maven or Gradle buildpack accordingly). In fact, there's nothing specially you need to do to run a Kotlin app on Heroku, so we have some docs and there isn't much more to say about it. We've also worked closely with the Kotlin folks to make sure the ecosystem plays well with Heroku. Let us know if you have any trouble with Clojure on Heroku. Stackoverflow.com is a great place to start (and I personal try to watch for questions tagged with "Heroku"…

We use PagerDuty and couldn't be happier with the product. Ops in a modern startup (based on my experience at Crittercism) is about 1/3 automation (deploys, backups, cronjobs, etc.) 1/3 monitoring, and 1/3 vendor/product eval (hosting, various consultants for things like database tuning) The hardest part about monitoring isn't making the tool go off, it's (1) knowing when something is broken and (2) knowing who needs to be alerted when that thing is not working. "Tell the whole team" breeds an attitude of "this is someone else's problem", and also prevents real work/progress from happening during incident response. You have to get away from the "all hands on deck" during an incident once your company gets beyond about 3-4 engineers or your feature velocity is going to get destroyed. Also, as your company gets larger, you'll find that managing the communication around the incident is just as important as fixing the problem. Customers HATE being left in the dark, so it's important to figure out who needs to know things are broken (internally and externally) and how that's communicated. Heroku did an excellent writeup on this topic recently: https://blog.heroku.com/archives/2014/5/9/incident-response-at-heroku -- even if you don't adopt the full system outlined there, at least ensure you're thinking about it, especially the communication part.

Heroku (I work there) recently announced support for .NET on the platform https://blog.heroku.com/dotnet-support-on-heroku

We’ve been working the next generation of Heroku - and actually also launching that this week! Check out our post on it here https://blog.heroku.com/planting-new-platform-roots-cloud-native-fir

Yeah, the lack of HTTP/2 support has been a long-standing issue with Heroku. They just shipped HTTP/2 terminated at their router [0], and have it on their roadmap [1] to support HTTP/2 all the way through. But it seems like it's at minimum a few months off. (As for VPC peering: the moment you need that, it sorta feels like Heroku is no longer the right place to be, even ignoring the costs.) [0] https://blog.heroku.com/heroku-http2-public-beta [1] https://github.com/orgs/heroku/projects/130

This can easily happen if you have multiple services that can write/update in the same table/rows and rely on database coordination instead of using an external queue like Kafka. Postgres (presumably other databases) can propagate these locks to table locks [1] and cause contention for the whole infra. [1] https://blog.heroku.com/curious-case-table-locking-update-query

> Potentially even embedded experiences so you could share reports internally without needing to actually log into Outerbase. Not OP, but this reminds me of Heroku Dataclips and I think you should strongly consider such a product feature. https://blog.heroku.com/how-dataclips-power-insights-at-heroku EDIT: Tremendous! Thanks for the reply!

3x increase when 3.0 is compared to 2.0[1]. I think it was largely achieved. [1] https://blog.heroku.com/ruby-3-by-3

An example is Ruby MJIT's: https://blog.heroku.com/ruby-mjit. I'm not a big fan of this strategy - as a matter of fact, Ruby's future (reference) JIT is a conventional JIT.

I guess this is what Heroku was pushing for [1] when client tokens were leaked. They wanted GitHub to adopt RFC 8075 [2], that combines mutual TLS auth with the tokens, so that the tokens can only be used by authorized clients, not just anyone that had possession of the tokens. [1] https://blog.heroku.com/april-2022-incident-review [2] https://datatracker.ietf.org/doc/html/rfc8705

I think they aren't in effect yet, but were announced in this blog post from last week: https://blog.heroku.com/new-low-cost-plans I am not sure if it will meet your expectations though, it doesn't really provide something much cheaper than 7/month or for an always-on production service. As I see it, the "eco" dyno is mainly a way to more easily save money with transient dynos (used for things other than production services) -- it does meet your concern about hobby dynos not sleeping though! There's also a new cheaper very limited postgres corresponding to the previous free postgres.

lol, this is a response for this a bit obfuscated first announce https://blog.heroku.com/next-chapter