And here I share my newest fun story (a video this time): An engineer as an ‘expert’ in a business/requirement meeting. The task is simple: create seven red lines. But the twist is that these lines must be perpendicular…
After two great APISTRAT events last year, the first European event in Amsterdam kicked things of this year – and duly delivered another great few days of content and discussions. The tweet stream says in all on how engaged people were: the keynotes and sessions just got better an better.
Well, you probably know my thoughts on cloud, PaaS, iPaaS and the like. In short, there’s a lot of hype around it, unscrupulous vendors, and some awesome magic involved. But there is some truth to it when you live in reality.
This week, Cisco put itself forth as a champion of policy-based networking, but it turns out VMware Chief Networking Architect Martin Casado has been looking in that direction. He started about a year ago. That’s when he got rolling with Congress, an OpenStack initiative that’s drawn the interest of IBM, among others.
With SDK 2.3, Azure SDK team got rid of “DSInit.exe” application and instead the new application for Storage Emulator is “WAStorageEmulator.exe” which can be found in “C:\Program Files (x86)\Microsoft SDKs\Windows Azure\Storage Emulator”.
One of the major conclusions revealed in the data from DZone’s 2014 Cloud Platform Research Report was a distaste for trade-offs. IT professionals don’t want to choose between the benefits of public cloud and the benefits of private cloud.
Just as continuous integration gives way to continuous delivery, IaaS naturally leads to PaaS. This is echoed by 2014 predictions that value will start to migrate “up the stack” from IaaS to PaaS. Let’s now turn our focus to PaaS and talk about what can and can’t be done with CI and CD on PaaS.
The popularity of cloud computing has been increasing rapidly since it was invented and the reason for this is that it has numerous benefits to offer. A majority of medium and small sized businesses are switching to cloud based solutions and owners are smiling all the way to the bank after the switch.
For those of us in the real world that have worked on business-critical integration projects, we know the cold reality. They suck. Coding them by hand is going to land us into a world of hurt. So if we’re smart, we leverage existing tried-and-true integration libraries like Apache Camel to do the heavy lifting.
What if we were able to set expectations beyond a simple number? What if we could say what we know and what we don’t know? What if we could give our best estimate now, and give a better one next week when we know more? Would that help?
Protoypes are good. Well I think so. They give you a better idea of how an application should hang together, where the abstractions are, where there are opportunities for refactoring and re-use. But are there downsides? The classic one is that a prototype sometimes becomes the production code.