I’ve never had the experience of an internship. Back when I started, you’d work under somebody’s wing for a week a max and that was it. No real internships. And so, every time we have students in our office, like we did three days ago at Cloud Night, I get slightly curious and envious. 🙂 I wish I had that too. A company that would open their offices just for me, introduce me to its teams, show me what they do, treat me like a professional, pamper me a little bit. And all that for my own growth, which would eventually lead to the company’s growth. Looks like a pretty fair chance to me.
Posts Tagged Under: cloud
It’s that time of the year again, when technology companies start opening champagne bottles, celebrating their products and success stories. We like bubbles very much as well, so we wanted to share some great news with you.
A recent IDC article stated that “There’s a $100B cloud in our future.” On paper, this looks like a huge opportunity and it’s backed up by big trends such as the distributed enterprise, the proliferation of devices needing to access enterprise networks, IT assets being managed remotely and big data and apps to mention just a few. While these opportunities are obviously real, when service providers try to sell to SMBs, the situation is not that clear-cut.
Verb Days 02 is over and it’s pretty obvious now that we have improved quite a bit since our last internal hackathon. Everyone had fun, worked hard and … focused more on presentations. We’ve learned a lot for the next events.
From the dust of old centuries until today’s computer-driven and smartphone-glued society, seven has always been considered a magical number. Many believe in the power of seven, be they sorcerers or mathematicians, historians or, in the past decades, even psychologists. Seven days in the week, seven wonders of the world, seven primary colors, seven notes in the musical scale, seven ages of man, Miller’s law on human brain’s capacity of processing information, and the list can go on and on.
There is no apparent connection between these two, but Moonshot is actually in the same trend, even though it uses Intel x86 (Atom). Many people advocate for ARM on servers, mainly because it is low-power, allowing a high CPU count per rack. But no one would mind I guess with a low-power CPU from Intel either.
Unfortunately, not many have a good overall picture on the cloud challenges, not to mention software engineering. And this is pretty complicated.
With a weather as sunny as this, who would stay indoors? Definitely not Johnny! 🙂
Check out this week’s problem to see what it’s all about. As always, keep in mind the rules and send us your solutions here by Tuesday, April 23rd, 10:00 AM GMT! Good luck! 🙂
Keep in mind that the competition is almost over! We will have only one more problem next week.
We can’t kick off the weekend without a brain twister, can we? 😀 Here’s our third problem to keep you company by Tuesday, April 16th, 10:00 AM GMT! That’s the deadline to submit your awesome solutions. Do not forget about the rules and submit your results here.
The Cloud Warehouse
Undoubtedly, you are familiar with cloud storage. Still, have you ever wondered how they are designed? To find out, you need to address some of the problems that are most frequently encountered while such a model is being shaped.
It’s a commonly accepted fact that in order to succeed in something, you have to surround yourself with people and ideas that push you in the right direction. To that effect, I want to make it clear that, when you become a 4PSA Clouder, nothing can stop you from becoming the next rock star in software.
The Early Years
When I started writing code for a living, everything seemed freakishly complex. Why? Because there was no one around to guide me through the rough terrain of learning different APIs at once, to point out the mistakes in my design, and offer advice on how to code better and faster.
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.
