Many of our objectives here at Push are intended to improve the stability and resilience for applications. An objective shared by the Reactive Manifesto: “[Resilient Apps remain] responsive in the face of failure. This applies not only to highly-available, mission critical systems — any system that is not resilient will be unresponsive after a failure….
Cloud storage is cheap and gets cheaper every day. In January, AWS announced yet another price cut (its 51s to be exact) for select instances. Google hit back criticizing the cut, however even with the January price cuts, Google Cloud Platform is between 15-41 percent less expensive than AWS across several comparable instance types. That’s great…
Ever on the lookout for book recommendations, especially for interesting and educational works, I asked our London office what non-fiction or technical book they are reading at the moment. These are some of the answers I got: Martin is reading Flash Boys: A Wall Street Revolt by Michael Lewis Martin says: “This book was recommended…
Event-driven data is data that is sent or received based on something that happens. For computer programming, that could be a click of a mouse, typing, etc. For apps, it can be similar, but we focus on event-driven data as something that happens outside the app, that impacts what the user will do e.g. there…
The exploding world of real-time data integration has led many to ask what technologies represent the best choice for their application architecture and how real-time data delivery platforms can help. There are several competing vendors – but not all are created equal. In this post, we’ll discuss the differences between Server-Sent Events and the WebSocket…
We have strong opinions here at Push on when REST APIs can be harmful to an app – namely how it can impact a system’s scale, throughput and performance. While REST APIs are tried and trusted for downloading web pages, most mobile and web app users are used to having information delivered to them proactively…
In 1967, Melvin Conway published a paper that asserted system design often reflected the communication structure of the organization building said system. This often meant that larger co-located teams developed monolithic systems, while smaller distributed teams built more loosely coupled systems. However, Conway also found that the initial design of any system was almost never…
One of the biggest questions when building an enterprise software solution is whether that solution is ready to go into production. When is enough testing enough? When have all the risks been mitigated? When are you ready? Diffusion is a powerful ingredient software, but it is only one part of a larger solution that can…
Application or enterprise architecture has become a fast moving world of late, with many voices talking loudly and often about technology choices, integration patterns, standards, etc. Yet throughout all this noise, one simple rule prevails – you must limit coupling between services, and especially between frontend apps and backend resources. Unfortunately, we often fail to…
Since my last post about Diffusion’s support for high availability (HA) we have made substantial changes to how we replicate data in our latest release, Diffusion 5.6. I’ve already written a little about session replication, topic replication and how we use Hazelcast so I will focus on updating you with the latest changes. We’ve done the…