2 Burst results for "Plato Oregon"

"plato oregon" Discussed on Ruby on Rails Podcast

Ruby on Rails Podcast

05:13 min | 1 year ago

"plato oregon" Discussed on Ruby on Rails Podcast

"Welcome to part two of my interview with Robbie Russell. Today will dig into the results of the twenty twenty ruby on rails community survey. So. Robby. Great to have you back and I'd love to start off by asking you why planet Argonne conducts the survey. Questions. So when I have to answer every few years, even to my own employees, like why are we doing this and so the the origin story isn't the first several years of employees, Plato Oregon being a part of the ecosystem we part of our service offerings was hosting for rebels, applications and. So two thousand I think it was two thousand eight to give or take we. We were we were realizing that we're lagging kind of investing and keeping up with some of the new ways of how servers and such were being managed how applications would be deployed, and so we really let's write a survey of the community to get a sense of how people were currently hosting how much they're spending on hosting and what versions of rails. They're using a bunch of other little tidbits related to that. So that kind of like help and we promise that we would share all the results of everybody minus everybody's email address. So that way we could be okay. Here's kind of like the state of the industry when it comes to deploying rail. So that was our first version of that survey and through. That survey admittedly, we realize, okay, we're way behind on a number of these kind of advancements in the deployment world. So we ended up saying we're going to basically kill off our hosting part of our business and we ended up selling that to another organization in we're just GONNA focus on coding related projects and consultative services there. So that's how it started. and. So two years later like Oh, let's do it again but we're going to modify to be a little bit more inclusive, just the broader community and we got rid of some of the questions related..

Plato Oregon Robbie Russell Argonne Robby
2020 Ruby on Rails Community Survey with Robby Russell

Ruby on Rails Podcast

05:10 min | 1 year ago

2020 Ruby on Rails Community Survey with Robby Russell

"Today will dig into the results of the twenty twenty ruby on rails community survey. So. Robby. Great to have you back and I'd love to start off by asking you why planet Argonne conducts the survey. Questions. So when I have to answer every few years, even to my own employees, like why are we doing this and so the the origin story isn't the first several years of employees, Plato Oregon being a part of the ecosystem we part of our service offerings was hosting for rebels, applications and. So two thousand I think it was two thousand eight to give or take we. We were we were realizing that we're lagging kind of investing and keeping up with some of the new ways of how servers and such were being managed how applications would be deployed, and so we really let's write a survey of the community to get a sense of how people were currently hosting how much they're spending on hosting and what versions of rails. They're using a bunch of other little tidbits related to that. So that kind of like help and we promise that we would share all the results of everybody minus everybody's email address. So that way we could be okay. Here's kind of like the state of the industry when it comes to deploying rail. So that was our first version of that survey and through. That survey admittedly, we realize, okay, we're way behind on a number of these kind of advancements in the deployment world. So we ended up saying we're going to basically kill off our hosting part of our business and we ended up selling that to another organization in we're just GONNA focus on coding related projects and consultative services there. So that's how it started. and. So two years later like Oh, let's do it again but we're going to modify to be a little bit more inclusive, just the broader community and we got rid of some of the questions related. We still keep that in their some of that in there, but we don't get into like budgets in the same way we used to we done so became. There weren't really any other surveys around the time that were really pulling the rails community to kind of get a sense of Persian rails you're running and how large is your team, and where are you and what gems are you relying on and which ones are frustrating to work with in what's keeping like, what are some of the challenges your teams having, and so it's became a thing. We started running every two years so that we could then share back with the community. And just to kind of get a pulse on where things were moving which tools. Use things in their related to what database servers you're using. And we can see trends over the years like their their services if you go. Over that time you could also, you can put the new survey results. You know you can go back to two thousand nine and compare every couple years and see that there are services that existed back. Then the no longer exists and nobody's using there's also scenarios where like I one point say squall was largely the most popular database in the community, and now it's completely flipped around where post grass is the most popular and I have some I understand why that's happened but. It's interesting to kind of see those trends over the over the years, and so it's more of a curiosity that we have in a way that we can every couple of years interact with the community and and kind of like catch up on a few different ways than than share that information back with the community again. Well. I. Think it's a fantastic project. You do a really great job of gathering the data and then turning around and displaying a very nice site in order to view that data. Of course, we will link all this in the show notes and listeners I suggest pausing the episode and reading over the results, and then we are going to dig into some surprises that I came across. A lot of the results were what I expected as Robbie noted post Gretzky while continues to dominate. The defacto performance monitoring tool and the folks that did take the survey which was over two thousand people wholeheartedly agreed that raises their server side framework of choice. So, for the one question, you are primarily building monoliths are micro services twenty five percent answered hybrid. and. So Robby, what circumstance would you take hybrid approach? So? That's a good one the. I'm always curious about. Work in the consulting world where we inherit and work on a lot of other people's projects and so quite often most rails applications likely unless they've started maybe in the last five take years. Are Likely to start off in kind of a Monolithic Forum. In Oh, let's move into a more of a micro services approached and so they start maybe. Breaking off pieces of it that way so I think it's it's. Just inherent in the kind of well, we WANNA start experimenting with micro services. So here's a segment of our application. We're GONNA break off. Move into do micro service. So I think that's that's how that comes about. You know I don't know if the I don't know what I expected. The numbers look like they're. In some ways I think I'm surprised that bashing maybe more not the more common answer like a higher number in some ways but. It's but I don't. I can't speak for everybody but it's kind of like my theories because a lot of evolution of iterating on an existing application like, okay. How do we start moving in this direction and then whether they're going to go like full micro services or Ni-, you know basically like strip back the core part of the application what have you but. I think that's someone of my theory

Robby Plato Oregon Argonne Robbie Gretzky