“Be more productive” is the work chant of the decade. And it’s unlikely to change anytime soon. The future is every bit about boosting productivity. Meanwhile, today has its own challenges. And it’s tougher than ever to stay ahead. Especially considering how quickly things change.
And these things are all related to technology. Indeed, tech has revolutionized the workplace. Granted, the past few decades have brought forth significant change. But we mean disruptive tech. Only two decades ago email on a mobile phone was a stretch. Tech is key, and it’s been transforming the workplace. But the constant is people. And people, unfortunately, can fall behind only to find themselves on the brink of burnout.
Besides, we might have reached an odd plateau. When compared to people, tech is no longer as disruptive as it used to be. At least, not when it comes to tech helping us be more productive. Because at the end the day, it’s the individual that deals with all the challenges. The constant here is the end-user. There’s only so much we can do in a day.
Posts Tagged Under: REST
Services offload their computationally expensive tasks into workers. Think of software that converts video from its original format to a web standard. This kind of job can be considered long-running, even for state-of-the-art hardware. The web app can’t convert the video, it doesn’t have access to the software and, even if it did, we’d have little control over what ends up on our servers. The service used by the app could convert the video, but it would take valuable processing time shifting though millions of requests.
As promised in our previous article, this post will be about the ways to optimize the response time from a web service when a client needs to read a resource. We are going to achieve this by not reading information on a resource if it has not changed. This helps developers create faster web applications.
VoipNow is a complex team, with different skills, from product management to support experts and sales, constantly growing and looking for more teammates. This article is about a new opportunity in the Software Engineering Unit. When it comes to choosing our colleagues, we are very picky. But if you’re very good, you will win us over in no time. 🙂
In a previous article, we described how to choose a HTTP method when implementing operations that affect resources. Today, we are going to explain how to implement services that manage concurrent operations on a resource and how clients should use such services.
The Problem
Sometimes, Apps must handle concurrent updates on a resource. Just imagine an application that acts like a Wiki, where users read, write, and edit articles.
We do a lot of REST in the Pineapple team. We love REST. Why? There are many reasons:
- It is standard, so that creating services always follows a pattern
- Developing clients is super easy, in all programming languages
- Programmers can easily understand it
- Testing (of all types) can be easily automated
- Because it relies on HTTP, it’s highly scalable infrastructure wise
- We can choose the preferred data format for sending and receiving information – usually JSON 🙂
