Many applications have the need for asynchronous or background processes to perform work outside of the standard Rails request/response lifecycle.
This series examines two interconnected topics: system design and the launch of new features in Rails applications. Don’t worry, this series is not about ivory-tower architecture. In fact, it is the polar opposite. Our goal is to help you rapidly develop amazing new capabilities with Ruby-on-Rails and get them in the hands of your customers.
For decades, engineers have been using the system time-based job scheduler cron to manage processes that run on a periodic basis. As applications move to container-based infrastructures, teams are faced with the decision of how to implement scheduled jobs in a Kubernetes environment. Fortunately, there are some very straightforward solutions for this common scenario.
At Engine Yard we are on a continuous journey to provide you with tools to minimize your operational burden, moving you towards friction free NoOps application deployments. Today we are pleased to share an exciting new capability which was one of the top asks from our Ruby community. Yes, we are talking about support for containers in Engine Yard.
When you need customized enterprise solutions, do you tend to hire the expertise you need to develop the necessary applications or do you contract it out? When you consider that added overhead of hiring a full-stack developer salary, you may find it more cost-effective to rent the expertise you need rather than hire it.
Management is not about being in charge. We usually associate the term “manager” with people managers. At first glance, a people manager’s job consists of bossing people around – telling them what to do. For example, engineering managers no longer write much code…
Send us a quick note and someone will be in touch soon.