Future of Cloud-Native Computing
Tuesday, September 14, 2021
Why are enterprise organizations making a move from on-premise solutions to completely cloud-native? What does that mean for improving, scaling, and securing their CI/CD pipelines? And what exactly is continuous packaging, anyway?
Join Cloudsmith’s Dan McKinney in this session as he answers all of these questions, helping attendees understand the true difference between cloud-hosted and cloud-native, how to get started with migrating to a cloud-native solution, and the true benefits of being entirely within the cloud.
The data revolution is upon us, and, well, has been for several years. It comes as no surprise that as application technology has evolved to keep up with the ever increasing expectations of users, the data platforms and solutions have had to as well. A decade or so ago we thought all our problems had been solved with a new player in the game, NoSQL. But, spoiler alert, they weren't.
In this session we're going to dive into a brief history of data. We'll examine its humble beginnings, where we stand today, and how modern relational databases will shape the cloud landscape going forward. Throughout the journey you'll gain an understanding of how SQL and relational databases have adapted to pave the road for a truly bright future.
OPEN TALK: Unlock Cassandra Data for Application Developers Using GraphQL and REST APIs with Stargate.IOJoin on Hopin
Cassandra is an incredibly powerful, scalable and distributed open source database system. Companies with extremely high traffic use it to provide their users with consistent uptime, blazing speed, and a solid framework. However, many developers find Cassandra to be challenging because the configuration can be complex and learning a new query language (CQL) is something they just don't have time to do. Stargate is an OSS multi-model API Data Layer for cloud native databases which sits on top of Cassandra and provides HTTP interfaces to your data - it provides a REST API, a GraphQL API, and a document-oriented Schemaless API. You can install it on top of your own Cassandra instance and participate in the community. During this presentation we will demonstrate and share the purpose, capabilities and internals of Stargate. We also give a working sample as a docker-ready configuration file.
You’ve heard of Serverless but you really aren’t sure what it is about. Isn’t serverless just another word for cloud computing? Isn’t it just “Other People’s Computers”? Or is it the most efficient way to develop applications, letting the developer focus on their own priorities instead of anything to do with the administration of a server? Cloud providers would have you believe it means letting them take care of the platform side. But the idea of Serverless extends beyond the platform to encompass everything from microservices to databases, from development to operation, from storage capacity to the network. This talk is geared towards those curious about this new Serverless technology and what opportunities arise by embracing the latest movement.
After the rush to take advantage of cloud native application development and tools like Kubernetes, DevOps teams now have a lot more to think about. In many cases, DevOps adopted early continuous integration/continuous deployment (CI/CD) pipeline tools such as Jenkins, and are now attempting to apply them in cloud native scenarios where they aren’t the appropriate fit they once were. Cloud native pulls the developer down to infrastructure-related operations, and the current CD tools cannot help bring back the application-level context that developers once had before moving to a microservices architecture – hence, adding more complexity to the development workflow and observability of applications post-deployment. DevOps teams also face new challenges in application policy management, especially so in closely regulated industries, as they adapt their processes to establish trust and security in cloud native environments. At the same time, DevOps needs to reevaluate approaches to automation and strategies for eliminating human error, as cloud and Kubernetes deployments have ushered in a return of very manual and tedious efforts.
This session digs into details around three cloud native 2.0 strategies that DevOps teams ought to consider sooner than later to stay on top of a fast-changing ecosystem: 1) how to build CI/CD pipelines with greater interoperability and composability, 2) how and why to harness application policy management, and 3) how to balance automation and audits
The new LAMP (Linux, Apache, MySQL, PHP) is a collection of modern, developer-friendly APIs. The first generation of enterprise APIs were designed to expose slow moving legacy apps. Modern APIs must move at the pace and scale of microservices. This offers a huge opportunity to modernize internal systems to be API first and developer friendly. In this session the speaker will consider the relevance of internal v. external APIs for refactoring legacy apps. Attendees will learn to build a catalog of internal APIs to use as building blocks when developing new apps and discover how to navigate the noisy market of API offerings to find the best fit solution.
The CNCF project OpenTelemetry is increasingly becoming the standard for getting reliable and consistent application and machine data to your monitoring and observability tools. Many organizations are realizing the power of decoupling their metric, log, traces and span data collection from their monitoring stack. Giving them more freedom, and capabilities, to improve the observability of their application. Allowing organizations to be more consistent and have more confidence in supporting their applications. In this session learn about.
1.) What is OpenTelemetry
2.) What is the architecture of the OpenTelemetry Collector (OTel)
3.) How do you build a strategy around OpenTelemetry
4.) How do you get started with OTel
Standardizing on OpenTelemetry makes your application more observable, and helps your organization implement better observability and monitoring practices.
In today’s fast-paced business and technology environments, an organization should never find itself boxed in by limited options for adapting to changing requirements or improving its workload strategy.
The Five Pillars of the AWS Well-Architected Framework—Operational Excellence, Security, Reliability, Performance Efficiency, and Cost Optimization—provide a way to consistently measure operations and architectures, identify areas for improvement, and respond to evolving requirements or external issues. The goal of the framework is to help architects learn the process of making informed, value-add decisions that reflect the organization’s priorities.
In this Q&A session, Excellarate’s Mike Watson hosts Hamdy Eed, an AWS Senior Solution Architect, for a lively discussion about putting the pillars into practice. They’ll explore how to navigate tradeoffs, a crucial function of the framework in guiding organizations through the process of shifting focus and priority among the pillars as needed. And Mike will ask Hamdy to talk about the latest tools and innovations available in the market to augment the implementation of each pillar.
Walk away with a better understanding of how the AWS Well-Architected Framework will help you learn how to:
~Design and implement scalable architectures that align with AWS best practices.
~Effectively utilize computing resources to maintain efficiency when system requirements change or technologies evolve
~Expand options with a structure that weighs priorities and adds business context when evaluating the trade-offs of each decision
Wednesday, September 15, 2021
In 2021, your entire tech stack is likely in the Cloud - so why aren’t your software packages?
Whether you’re currently on-premise, have your own in-house solution or have a bit of a hybrid set up, join us in this session to explore why the future is cloud-native, what the benefits of this are over cloud-hosted, and how to easily set up a secure, cloud-native software pipeline in 60 seconds.
Today’s pace of change is relentless. Customers expect organizations to respond to their needs immediately, with services that are tailored to them. New competitors appear out of nowhere and reshape markets overnight. Global events cause demand to surge in one area and evaporate in another, creating pressure on every aspect of business, requiring the ability to adapt and perform in real-time.
In this environment, success requires more than size and scale. It requires using applications and data to deliver rich, personalized experiences; to get the right data to the right person at the right time—no matter where it’s stored. And to do it all with greater efficiency, security, and speed. In an age when businesses are trying to disrupt the world, and the world is disrupting business, organizations have to move faster, smarter, and with greater operational efficiency…or risk being left behind.
Cloud is reshaping the way EVERYTHING is done in today’s world. We see it in our personal lives, where we expect a graceful operation between our own devices and what’s happening “out there” in the cloud. Why should an enterprise organization be any different? They need that graceful operation to ensure the speed and efficiency they’ll need to keep up. For a business, cloud is key – and the only way to move fast is to use the cloud, operate like a cloud, or both.
And when it’s both, organizations need the best of both worlds. They don’t have time to figure out how to do it one way in their own data center, and then a completely different way in the cloud. In short, they need the same way to acquire, consume and operate no matter where they are.
The demand for cloud has never been higher.
- A report from Canalys on Q3 spending shows a significant jump in worldwide cloud spending, up 33%.
- IDC expects that by the end of 2021, 80% of enterprises will put a mechanism in place to shift to cloud-centric infrastructure and applications twice as fast as before the pandemic.
- For NetApp, in Q1 FY21 earnings our cloud business grew 192% YoY.
To instantly adapt to a rapidly changing landscape, our customers need to have access to the right data, at the right time, in the right place—at the right pace.
- We see organizations looking at solutions from cloud providers for two important reasons:
------ First, is to lower their I.T. cost because they're facing economic challenges and they want to move to cloud as a mechanism to get a more efficient and agile I.T. infrastructure. -------- Second is the shift to digital. People want to get new innovations to change their business model.
- The future of innovation lies in our ability to harness the power of the data that is available to us, and to act on that data to transform. Companies that do this effectively will thrive.
----- Whether it’s a retailer looking at e-commerce, a financial institution looking for new ways to use data to identify business opportunities or a manufacturer l using sensor technology and I.T. to change their manufacturing shop floor, all of them eventually boil down to unlocking new business models using the power of data.
----- Every customer is in a different place on their journey to cloud – with a different set of imperatives and challenges. But across the board, a few things are clear--as we’re hearing directly from our customers, every day. Data is at the heart of everything our customers do.
I've seen so many developers failing when they tried to think new apps for the cloud or when they needed to move an existing app over there. In this (short) session we'll talk about some (mostly non-technical) topics to consider to think like a Cloud Architect.
As engineers, once we start having more than one (micro)service or product in our architecture, we think about sharing code, functionality and having seamless user experiences between systems; that’s the start of a platform! But we have so many decisions to make:
* What features are part of the platform, and when?
* Do I go lightweight with drop-in libraries that are quick to adopt or heavyweight like frameworks for a better developer (and user) experience?
* How do I make my platform extensible and maintainable?
* How can I address the classic hockey-stick adoption pattern on your services?
* How does Conway's Law apply to the platform?
In this talk we describe a number of patterns (and anti-patterns) for designing a platform we’ve seen and implemented both from industry and as part of the platform powering Atlassian Cloud.