5 ms·

"Java, .Net, Ruby, Node, Python, PHP, etc." Does that "etc" include Clojure and Scala?

by dsrguru 14y ago

rmason 14y ago
How about Railo or OpenBD? Please.
human_error 14y ago
"MySQL, Mongo, PostgreSQL, etc." I'd like to know what that "etc." stands for.
- lucperkins 14y ago
  The "etc." simply means that we're looking to expand the number of database options over time beyond this list
  - biot 14y ago
    Rather than saying "etc." which makes it look like there are additional databases you currently support but are not listed, why not change it to "and more on the way" which clearly communicates what you mean?
- Poiesis 14y ago
  PostgreSQL does not seem to be available, despite their ad copy. Googling reveals that it's been in beta and they seem to be expecting to roll it out soon.
suresk 14y ago
Since Clojure and Scala both compile to Java bytecode, I would assume so.
rabbitfang 14y ago
I would hope so. Perhaps they should call those out to make it clearer?
edwinnathaniel 14y ago
No Documentation on how to use Java. Googling for AppFog Java gave back broken 404 links to github.
- lucperkins 14y ago
  Java documentation is on the way soon
  - edwinnathaniel 14y ago
    Tomcat, Jetty, or GlassFish? Heroku Java deployment is "unusual" and there are many Java developers out there that prefer WAR/EAR that complies with JEE5 (legacy purpose) or JEE6. If you can achieve that, get ready for massive users, I know there are people who don't like GAE model for various reasons. Basically: make it like Jelastic and don't limit it like CloudFoundry (no EJB 3.1, etc etc). JavaEE deployment model is preferable over some "weird" setups.
    - lucperkins 14y ago
      I'm not much of a Java person myself, but our dev team has told me that the WAR + Tomcat route tends to work best on AppFog, at least at this point in time. This is also our recommended way of running other JVM-based languages.
      - edwinnathaniel 14y ago
        Your dev team is spot on. The Java market does not have a solid Cloud Platform so far because most vendors go their own way to support Java (Heroku and CloudFoundry are the example of going their own way). The only Java-friendly PaaS so far is Jelastic simply because they support GlassFish and Tomcat utilizing standard deployment model. But Jelastic does not provide the infrastructure (data-center or AWS, whichever), they partner with hosting providers, which I think is not a great move. If AppFog can come up with a more standard/sane Java PaaS model out there, you guys can win that particular market. If I may suggest more: 1) Tomcat 7 instead of the older 5 or 6. The JavaEE landscape has changed significantly from J2EE 4 to JEE 5 to JEE 6 in which each major version moves toward _way_ less code and reduce XML/settings/configurations to a very minimum. 2) TomEE (if possible, or as "add-on"/next-level offerings) Tomcat 7 implements a subset of JavaEE 6 (known as the "web-profile": Servlet[controller], JSP[template], JSF[view/controller], Dependency Injection, JPA[orm]) Enterprises who are still in love with EJB 3.x need TomEE. 3) Maven for deployment (feature/option) Use Maven for deployment.

"Java, .Net, Ruby, Node, Python, PHP, etc." Does that "etc" include Clojure and Scala?

by dsrguru 14y ago

"Java, .Net, Ruby, Node, Python, PHP, etc." Does that "etc" include Clojure and Scala?

rmason 14y ago

How about Railo or OpenBD? Please.

human_error 14y ago

"MySQL, Mongo, PostgreSQL, etc." I'd like to know what that "etc." stands for.

lucperkins 14y ago
The "etc." simply means that we're looking to expand the number of database options over time beyond this list
- biot 14y ago
  Rather than saying "etc." which makes it look like there are additional databases you currently support but are not listed, why not change it to "and more on the way" which clearly communicates what you mean?
Poiesis 14y ago
PostgreSQL does not seem to be available, despite their ad copy. Googling reveals that it's been in beta and they seem to be expecting to roll it out soon.

suresk 14y ago

Since Clojure and Scala both compile to Java bytecode, I would assume so.

rabbitfang 14y ago

I would hope so. Perhaps they should call those out to make it clearer?

edwinnathaniel 14y ago

No Documentation on how to use Java. Googling for AppFog Java gave back broken 404 links to github.

lucperkins 14y ago
Java documentation is on the way soon
- edwinnathaniel 14y ago
  Tomcat, Jetty, or GlassFish? Heroku Java deployment is "unusual" and there are many Java developers out there that prefer WAR/EAR that complies with JEE5 (legacy purpose) or JEE6. If you can achieve that, get ready for massive users, I know there are people who don't like GAE model for various reasons. Basically: make it like Jelastic and don't limit it like CloudFoundry (no EJB 3.1, etc etc). JavaEE deployment model is preferable over some "weird" setups.
  - lucperkins 14y ago
    I'm not much of a Java person myself, but our dev team has told me that the WAR + Tomcat route tends to work best on AppFog, at least at this point in time. This is also our recommended way of running other JVM-based languages.
    - edwinnathaniel 14y ago
      Your dev team is spot on. The Java market does not have a solid Cloud Platform so far because most vendors go their own way to support Java (Heroku and CloudFoundry are the example of going their own way). The only Java-friendly PaaS so far is Jelastic simply because they support GlassFish and Tomcat utilizing standard deployment model. But Jelastic does not provide the infrastructure (data-center or AWS, whichever), they partner with hosting providers, which I think is not a great move. If AppFog can come up with a more standard/sane Java PaaS model out there, you guys can win that particular market. If I may suggest more: 1) Tomcat 7 instead of the older 5 or 6. The JavaEE landscape has changed significantly from J2EE 4 to JEE 5 to JEE 6 in which each major version moves toward _way_ less code and reduce XML/settings/configurations to a very minimum. 2) TomEE (if possible, or as "add-on"/next-level offerings) Tomcat 7 implements a subset of JavaEE 6 (known as the "web-profile": Servlet[controller], JSP[template], JSF[view/controller], Dependency Injection, JPA[orm]) Enterprises who are still in love with EJB 3.x need TomEE. 3) Maven for deployment (feature/option) Use Maven for deployment.