Web stack selection
-
It's never that simple. It's not one size fits all. You always look at a variety of needs and then use the right tools for the job.
-
The bigger piece, why are you starting with a SQL back end? And do you mean SQL Server, or relational database? "SQL backend" isn't meaningful even when using buzz-style references as some people use SQL to mean "relational databases that can be accessed using SQL" and some people use it to mean "SQL Server."
-
WP if it meets all the goals and fits all the needs.
-
Oh read that wrong... Yeah it depends.
-
It was a bar conversation, we are just throwing around ideas. In our organization, our data will exist in internal MS SQL servers. Our task will be to write web applications to contextualize and work with this data (CRUD) and report for upper management and execs all internal information, nothing web facing. We have always just done everything Microsoft, because it is here and everything else in the environment is, however, I don' see many other people talking about or recommending it. I just wanted to see if there was a clear favorite, or a go to web dev environment that everyone agreed on. I kind of figured it depends would be the answer.
-
@s-hackleman said in Web stack selection:
It was a bar conversation, we are just throwing around ideas. In our organization, our data will exist in internal MS SQL servers. Our task will be to write web applications to contextualize and work with this data (CRUD) and report for upper management and execs all internal information, nothing web facing. We have always just done everything Microsoft, because it is here and everything else in the environment is, however, I don' see many other people talking about or recommending it. I just wanted to see if there was a clear favorite, or a go to web dev environment that everyone agreed on. I kind of figured it depends would be the answer.
So just some internal web front-end they see that pulls data to form reports from a MS SQL DB?
-
@s-hackleman said in Web stack selection:
It was a bar conversation, we are just throwing around ideas. In our organization, our data will exist in internal MS SQL servers.
Get it moved off before doing new development then!
-
@s-hackleman said in Web stack selection:
We have always just done everything Microsoft, because it is here and everything else in the environment is, however, I don' see many other people talking about or recommending it.
That's because it is generally crazy. SQL Server being at the worst of it. C# is okay if you stick to the really modern parts and avoid the cruft or lock in parts of it. But it's not great, just okay.
-
@s-hackleman said in Web stack selection:
I just wanted to see if there was a clear favorite, or a go to web dev environment that everyone agreed on. I kind of figured it depends would be the answer.
People should not agree, because there isn't one environment to rule them all. But there ARE environments that should be avoided, and the MS stack is certainly one of the more prominent ones that should generally be avoided. Think of web stacks as a filter - you want the list of what to avoid, then choose from the huge remaining pool for what to actually do.
-
For simple CRUD, PHP is often best. RoR, NodeJS, Python are all okay. Even Java is pretty good on the back end, but requires a lot more skills. Go2 is great and upcoming now. You have loads of choices that could all make sense.
-
@scottalanmiller oh I missed the CRUD part... i was thinking PHP too.
-
@obsolesce said in Web stack selection:
@scottalanmiller oh I missed the CRUD part... i was thinking PHP too.
RoR rocks on crud, too. And relational by convention.
