ANZ Pied Piper

I was recently at a presales event in Kuala Lumpur where they run my conference app (I will talk about the app in detail in a later post because it has played a key role in the Pied Piper program). One of my colleagues asked me about the backend the app uses. When I explained it was Redis he said that Redis doesn't have data persistent as is an in-memory database. There are two misconceptions about Redis: Redis uses key-value Redis is in-memory, therefore I can loose my data The first one is correct, but as we explained in the Redis article, the value side can be much more than just a "value", it can also take the form of a list, a set, a hash (which is essentially a dictionary) and more. So yes, you cannot do things a relational database can do, but with those 3 structures alone there are lots of use cases you can do ... and before I forget it is VERY fast. The second one is not true. When we looked at the different plans available in Pivotal Web Services (

The Pied Program program recently reached a major milestone; the completion of the enablement phase. Overall have covered 4 workshops that cover the pillars of the Digital and IT transformation: Agile and Cloud Native Apps, Automation, Internet of Things and Artificial Intelligence. Customers often see DellEMC Presales Engineers as trusted advisors. The knowledge we acquired through the program will help ensure we remain relevant in the context of the big wave that is shaking the market. To culminate this phase we asked the team members to work on a personal project that would help them internalise what we have taught so far.  This would be a competitive endeavour. They would be scored primarily on the use of all different skills with a minimum one skill from each workshop. This led to them adding features to their projects that looked unnecessarily convoluted or even not fitting naturally with the rest of the solution. We also scored creativity. At the end we saw a range of envi

As we have seen in previous posts Cloud Foundry Marketplace offers a large amount of services, including a variety of databases, message queuing, etc which will address the majority of use cases. However the offerings available in the Marketplace can be customized by the provider. For example the offerings from Pivotal Cloud Foundry might differ from Cloud Foundry on Azure or on Google Cloud Platform etc. In general each cloud provider will try to differentiate by extending the platform with whatever managed service they believe is unique to them and is going to help them attract customers. For example Google offers services like Google Cloud Storage, BigQuery, BigTable or the Machine Learning APIs, etc. Whereas Microsoft Azure offers Azure Storage, Azure SQL or CosmosDB in addition to Redis, MySQL or PostgreSQL. In any case, incorporating these services into your application should be done by reading credentials and other binding information from the environment so that we a