U.S. companies are desperately trying to recruit and hire skilled software engineers and developers, but there is simply not enough quality talent to go around. Tiempo Development is a nearshore software development company. Our headquarters are in AZ, but we are a pioneer and leader in outsourcing to Mexico, based on our three software development centers there. We have a proven process and we are experts at providing our customers with powerful solutions. We transform ideas into reality.
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome,” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
Summary: As a Developer, you cannot attach the debugger to your application in Production, but you can use logging in a way that helps you easily diagnose problems in both development AND Production. You also get to make friends with Operations people – win! The applications we're developing and running are becoming increasingly distributed, with requests crossing several service or container boundaries. The traditional debugger is of limited use in these scenarios, but with a solid, easy-to-use log aggregation capability in place, we can begin to explore ways of using logging to improve our understanding of how the software behaves in Production and enhance our ability to diagnose problems rapidly. Logging becomes not just a ‘dump' of exception or error details, but a rich trace of application execution.
Through WebRTC, audio and video communications are being embedded more easily than ever into applications, helping carriers, enterprises and independent software vendors deliver greater functionality to their end users. With today’s business world increasingly focused on outcomes, users’ growing calls for ease of use, and businesses craving smarter, tighter integration, what’s the next step in delivering a richer, more immersive experience? That richer, more fully integrated experience comes about through a Communications Platform as a Service which allows for messaging, screen sharing, videoconferencing and more. In her session at WebRTC Summit, Dr. Natasha Tamaskar, Vice President and Head of Cloud and Mobile Strategy and Ecosystem at GENBAND, will explore what’s next on the horizon and how to create amazing experiences by embedding real-time communications everywhere.
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery cycles and a poor customer experience.
WebRTC has had a real tough three or four years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong.
Of the many additions to Java 8 such as the Stream API and lambdas, I noticed one of the lesser talked about ones was CompletableFutures. So I decided to have a play around with them on the last Java component I wrote. My use case in a nutshell was piping large volumes of data from a distributed file system, compressing it and uploading to individual destinations on Amazon S3.
Change is hard, especially when it impacts organizational structure, legacy systems and processes. Our third annual software delivery survey reveals that the management of change is a long road as the majority of our respondents continue their implementation of Continuous Integration in 2015.
Azure is Microsoft’s cloud computing platform, a growing collection of integrated services—analytics, computing, database, mobile, networking, storage, and web. In the 12 months since Build 2014, Microsoft has delivered over 500 new Azure services and features, and greatly expanded the footprint and capabilities of what Azure delivers. Here’s a snapshot of Azure Allure, articulated by Microsoft exec Scott Guthrie, Executive Vice President of Cloud and Enterprise, at the Microsoft Build 2015 conference in San Francisco.
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
“Threats are always evolving and the days of ‘set it and forget it’ malware and virus scanners are over if you want to keep your business information secure,” explained Abel Sussman, Director of Federal Services at Coalfire, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff. Cloud Computing Journal: Security threats seem so widespread and diverse that it seems companies need a framework before they tackle individual issues. To what degree do you take this point of view?
Summary: As a Developer, you cannot attach the debugger to your application in Production, but you can use logging in a way that helps you easily diagnose problems in both development AND Production. You also get to make friends with Operations people – win! The applications we're developing and running are becoming increasingly distributed, with requests crossing several service or container boundaries. The traditional debugger is of limited use in these scenarios, but with a solid, easy-to-use log aggregation capability in place, we can begin to explore ways of using logging to improve our understanding of how the software behaves in Production and enhance our ability to diagnose problems rapidly. Logging becomes not just a ‘dump' of exception or error details, but a rich trace of application execution.
Thanks to Docker, it becomes very easy to leverage containers to build, ship, and run any Linux application on any kind of infrastructure. Docker is particularly helpful for microservice architectures because their successful implementation relies on a fast, efficient deployment mechanism – which is precisely one of the features of Docker. Microservice architectures are therefore becoming more popular, and are increasingly seen as an interesting option even for smaller projects, instead of being reserved to the largest, most complex application stacks.
Despite working in the digital space for years, now I was quite stumped a few weeks ago when I was asked to define it. Sometimes you can get away by circumlocution or to use the technically correct term, waffling. But given all the hype around digital transformation, I felt that it was a good time to try and get a working definition going. For one it helps to cut the hype. And two, clarifies what is NOT digital at a time when the label is being slapped around with abandon.
We really are moving in the direction of truly commoditized hardware. Some uses will always have specific requirements that are not mainstream and thus will require specialized builds, this is true in every industry. But increasingly, who made your hardware and where they got their parts from is a secondary issue. Which makes one consider what really sells hardware these days. Years ago when I was working for Network Computing, I reviewed a low-end blade server company capable of cranking up blades at a fraction of the cost of most vendors. They (like far too many good companies) ran out of money before they could grab market traction, but they did show that it could be done at a price even small enterprises could afford.
In the midst of Docker’s meteoric rise and the explosion of talk around containers, it can be easy to lose oneself in all of the new terminology and jargon. While we think about the challenges presented by using containers in production, we also continue to hear the metaphor of Pets vs. Cattle and why it’s important to maintain an infrastructure that acts like a herd of cows.
“Threats are always evolving and the days of ‘set it and forget it’ malware and virus scanners are over if you want to keep your business information secure,” explained Abel Sussman, Director of Federal Services at Coalfire, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff. Cloud Computing Journal: Security threats seem so widespread and diverse that it seems companies need a framework before they tackle individual issues. To what degree do you take this point of view?
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Azure is Microsoft’s cloud computing platform, a growing collection of integrated services—analytics, computing, database, mobile, networking, storage, and web. In the 12 months since Build 2014, Microsoft has delivered over 500 new Azure services and features, and greatly expanded the footprint and capabilities of what Azure delivers. Here’s a snapshot of Azure Allure, articulated by Microsoft exec Scott Guthrie, Executive Vice President of Cloud and Enterprise, at the Microsoft Build 2015 conference in San Francisco.
Change is hard, especially when it impacts organizational structure, legacy systems and processes. Our third annual software delivery survey reveals that the management of change is a long road as the majority of our respondents continue their implementation of Continuous Integration in 2015.
Thanks to Docker, it becomes very easy to leverage containers to build, ship, and run any Linux application on any kind of infrastructure. Docker is particularly helpful for microservice architectures because their successful implementation relies on a fast, efficient deployment mechanism – which is precisely one of the features of Docker. Microservice architectures are therefore becoming more popular, and are increasingly seen as an interesting option even for smaller projects, instead of being reserved to the largest, most complex application stacks.
August 10, 2015, saw the dawn of a new era at Google. It announced a huge restructuring of the company. An umbrella holding-company called Alphabet was created to manage a portfolio of separate companies each with its own CEO. Founders Larry Page and Sergey Brin elevated themselves to be the CEO and President of Alphabet with Eric Schmidt as chairman. The board will remain the same as before. For the biggest company Google, the new CEO is Sundar Pichai, 43 years old, who has seen fast rise in the ranks over his 11 year career. The other portfolio companies will be Nest, Fiber, GoogleX, Calico, Google Capital, Sidewalk, etc.
The amount of data processed in the world doubles every three years and a global commitment to open source technology is the way to handle this growth. An open technology approach fosters innovation through massive community involvement and impedes expensive vendor lock-in. This benefits buyers as markets remain more competitive. In doing so, open standards and technologies also allow for market hypergrowth, and this is the key to handling the growth of data. A doubling every three years means we'll be grappling with a full Yottabyte of data in the year 2040. That's one billion petabytes, an amount of data that, similar to pondering geologic time, I can understand in the abstract but not truly grasp. Meanwhile, the nature of this data—which can truly be called Big Data in today's age of the Zettabyte—is transforming from a jet plane model to a chewing gum model. By this I mean Big Data in its original conception 20 years ago referred to a small number of massive files, the type found in meteorology and nuclear-bomb building. Tomorrow's Big Data will largely be a product of billions of sensors, transmitting less than 10K at a time. Rather than thinking about a few 747s, we'll be thinking about billions of pieces of chewing gum. Already There We're already in such a Little Big Data era, with stuff like Hadoop and NoSQL databases equipped to handle the onslaught of data volume, variety, and--because of much this data's real-time nature—velocity. But we've only just begun. Innovation must continue apace, in hardware even more so than software. Today's technology already requires more almost 3% of the world's electricity grid to power its data centers—exponential increases in data processing simply will not be met by the global electricity grid in the absence of vast new hardware efficiencies. The OPG Thus I'm involved with something called the Open Performance Grid, or OPG. Announced in San Francisco in August 2015, the Open Performance Grid measures openness, performance, and leadership of hardware, software, and designs for modern data centers. The OPG is a community effort with input from technology users and buyers, analysts and researchers, and vendors who wish to compare their own self-assessments with what the community is saying. Sample measures of openness, beyond simple open-source availability, include the presence, size, and activity of a community and foundation for a particular technology. Market share, benchmark performance, and what we call the Innovation Curve are also part of the mix. Software categories include operating systems, virtualization, containers, PaaS, IaaS services and stacks, monitoring/analytics, management consoles, software-defined storage, SDN, SDDC. For hardware, we're looking at chips, boards, subsystems, and even overall data center designs. The challenge of meeting the astounding growth in data is enormous. The Open Performance Grid is a way to encourage and enable the technology provider, development, and user communities to meet the challenge. Contact me on Twitter to learn more.
We chat again with Jason Bloomberg, a leading industry analyst and expert on achieving digital transformation by architecting business agility in the enterprise. He writes for Forbes, Wired, TechBeacon, and his biweekly newsletter, the Cortex. As president of Intellyx, he advises business executives on their digital transformation initiatives and delivers training on Agile Architecture. His latest book is The Agile Architecture Revolution. Check out his first interview on Agile trends here.
There are many parallels to Google’s move to set up Alphabet as a holding company to remain at the forefront of innovation and what is required by all companies to foster innovation in the age of the Cloud and IoT. No one will argue that Alphabet was a change Google needed to make to remain relevant, fresh and innovative across a number of product initiatives. Under the Alphabet structure, Google provides operating divisions with the freedom and accountability for making decisions all while being nimble and quick on their feet. And perhaps most importantly, keeping their most creative people engaged and well…creative and not stifled by red tape and bureaucracy.