{"id":955,"date":"2015-09-28T14:44:36","date_gmt":"2015-09-28T18:44:36","guid":{"rendered":"https:\/\/www.redline13.com\/blog\/?p=955"},"modified":"2022-01-03T20:01:10","modified_gmt":"2022-01-04T01:01:10","slug":"redline13-newsletter","status":"publish","type":"post","link":"https:\/\/www.redline13.com\/blog\/2015\/09\/redline13-newsletter\/","title":{"rendered":"RedLine13 Newsletter"},"content":{"rendered":"

RedLine13 Just Got Real<\/h2>\n

RedLine13 started from a need\u00a0to support 50,000 users registering in minutes. \u00a0 The load testing market has been full of large, expensive,\u00a0closed, and\u00a0locked-down providers. \u00a0 There was no way for RunSignUp to scale without a large\u00a0investment for initially a point in time need. \u00a0Stephen Sigwart and Bob Bickel decided they needed to build something quick for their business. \u00a0Afterwards, they realized they had something\u00a0special – easy, inexpensive, and rapid load testing. \u00a0 Getting together with Rich Friedman they decided that this could be launched into an online service with support for open source projects such as JMeter and Gatling. \u00a0Now fast forward.<\/p>\n

\"RL13<\/a><\/p>\n

Until recently RedLine13 has been a side project to determine if there was something that others could use. \u00a0 We have realized that mission with over 1,500 users and 18,000 load tests run. \u00a0To determine if this is also something\u00a0a business could be built upon,\u00a0we introduced a low-cost subscription and have continued to see a lot of adoption.<\/p>\n

What’s next for us?<\/h4>\n
    \n
  1. More time on RedLine13.<\/strong> Rich has gone from side project support to almost full-time support. \u00a0 While he will still do some consulting for a few select companies (MeetMe where\u00a0he is still enamored with the technology team, RunSignUp where he is going docker crazy, and others) he is now full time wearing many hats.<\/li>\n
  2. Features.<\/strong>\u00a0 We are building the roadmap based on\u00a0customer feedback. \u00a0 Get on board as a customer and drive the roadmap for (Almost) free load testing.<\/li>\n<\/ol>\n

    Where do we fit?<\/h4>\n

    \"fit\"<\/a><\/p>\n

    We have now worked with many companies and have learned a lot. \u00a0One surprising item is how and where we fit with other\u00a0services. \u00a0Our goal is not to be the enterprise load testing tool, but we understand for many there is a need for high-end capabilities. \u00a0(Almost) free load testing is not the slogan for that kind of company.<\/p>\n

    Some\u00a0customers are sandwiching us between tools like Soasta, HP LoadRunner, \u00a0Blazemeter and their need for quick, repeatable, and cheap load testing. \u00a0We are fine with this and think there is a strong need. \u00a0Plug us in with Jenkins so you can test day in and day out.<\/p>\n

    \n

    Recent Blog Posts<\/h2>\n

    \"Continous_Delivery_by_Jez_Humble_and_David_Farley\"<\/a><\/p>\n

    A recent talk at FOSSCon 2015 gave rise to a series of blog posts.<\/p>\n

      \n
    1. Common Sense of Load Testing<\/a><\/li>\n
    2. What we measure with Load Testing<\/a><\/li>\n
    3. Simple Load Testing Process<\/a><\/li>\n
    4. Joys and pain of load testing<\/a><\/li>\n
    5. When do we load test<\/a><\/li>\n
    6. Scaling load tests old way<\/a><\/li>\n
    7. Scaling load tests new way<\/a><\/li>\n
    8. How we monitor the results<\/a><\/li>\n
    9. Review of the Open Source Load Testing Tools<\/a> such as JMeter, Gatling, The Grinder, and many others.<\/li>\n
    10. Why integrate load testing with\u00a0continuous delivery tools<\/a> such as Jenkins<\/li>\n<\/ol>\n
      \n

      New Features and Website<\/h2>\n

      \"siteupdate\"<\/a><\/p>\n

      We are working on improving the site around (Almost) Free Load Testing. \u00a0With each iteration, we hope to provide improved knowledge and ease-of-use. \u00a0 Here are some updates we deployed.<\/p>\n