Let’s say your web-application communicates with a 3rd party service and this service is somewhat fragile. Either because of its fragility – or for some other reason – under no circumstances do you want your application to bombard this service with concurrent requests. Whenever a component needs to make a request to this service, and there is already another request waiting for a response, the new request should wait until the previous request completes.Continue reading
Congratulations to our client Vroom.com for successfully securing a new round of funding worth $30M – a great start on the road to the larger goal of raising $70M over the next few months. Vroom, for whom Boyle Software has done work since 2016, has restructured this year in a push for profitability.
We wish our partners at Vroom continued success in their pursuit of being the best online marketplace for used automobiles. We are proud to be a part of the team!
Over the past several months, we’ve had a number of developers join our team in New York and Ukraine, but we’re constantly growing and we are still looking for more! Continue reading
Sometimes we need to make calls to some RESTful APIs from an AWS Lamda function. Let’s say we use Node.js as our platform. On the surface, there are two ways to do it: Continue reading
With innovative use of IoT sensors and smart, real-time reporting, New York City-based Energy Metrics is building a great business helping clients achieve significant power and dollar savings. Concentrating on three key real estate-centric verticals – financial institutions with retail outlets, hotel chains, and co-location data centers – EM is showing companies a path to greater energy efficiency and big savings on their bottom line. And Boyle Software is lucky to have EM as our latest client!
It certainly took me a while to get used to things – wrapping my head around the whole non-blocking nature of the Node runtime and how it uses a single thread to process requests – and how important it was that I definitely do not block that thread! Continue reading
- dealing with a whole bunch of endpoints in a typical application
- performing multiple roundtrips to the server for multiple resources in order to get data for a single page of the UI
- getting the request parameters right
- dealing with api versions – coupling between the client and the responses from the server
- over-fetching of information that is not needed