Modernization is a team sport where end-user, line of business, and IT systems need to come together with a single goal in mind, “ease of use and improving user experience.”

By Ernese Norelus , Eduardo Patrocinio, Oliver Senti

This current installment is part two of a multi-series blog; we go deeper into applying the application modernization approach. It will leverage IBM Enterprise Design Thinking, Event Storming, Domain-Driven Design, and Event-Driven Architecture. We are drawing on an exemplary approach to the Garage Method to enable application modernization projects at scale by applying a compelling application modernization journey to the Cloud.

Why modernize?

Without a doubt, this should be your first question. “Why do I need to modernize my applications? What do I gain from this?”; modernization is a costly and risky endeavor. Frankly…

Modernization is a journey, and it starts with the user experience in mind. It must draw a parallel between the organization’s future and its operational complexity.

By Ernese Norelus, Sreeni Pamidala, and Oliver Senti

Creating a business case for an application modernization project: business requirements change, and businesses need to transform towards a digital model to realize opportunities that were never obtainable before the emergence of the cloud. These days most relevant companies build their entire business strategy around cloud capabilities to capture their market share, building capability around customer experience, usability, accessibility, and are taking things further and using customer data to personalize outreach.

Introduction to site reliability engineering (SRE) and how you should monitor and keep your systems fast and reliable as they scale.

By Ernese Norelus and Erhan Saygi

Figure 1: Building SRE from Scratch

In the cloud era, customer experience is the new mantra for any serious business, a mission statement. The customer experience, usability, and accessibility are determined at the edge, where websites are expected to be always available [24/7/365]. Reliability is what matters after all for the users; an unused app has no value to the users and the business.

These days, every company is a technology company that drives transformative changes. Companies build their entire business strategy around cloud capabilities. Making this a significant operational challenge for them. Any degradation of performance and customer experience…

Build & Deployment processes in a real-time cloud-native project with a Kubernetes CI/CD approach for the enterprise with Serverless Jenkins (Jenkins X).

Figure 1: Jenkins X Architecture

The new era of DevOps is about the change that brings developers, IT operations, quality assurance, and business together with a common goal to get projects out faster and of better quality while focusing on collaboration as an extension of the agile principles. Speed is the new norm in software development, driven by an intensifying competitive market, where businesses have to deliver value quickly via software. Having the right culture, tools, processes, and DevOps best practices in place to accelerate the pace of application creation and enhancement is paramount. Now, we need re-imagined CI/CD for cloud-native applications on Kubernetes powered…

DevOps is not something you buy; it’s something you do.

DevOps is a re-organization practice that focuses on automated environments, provisioning, and process improvement to reduce cycle time by removing bottlenecks and also an organizational culture shift that promotes breaking down silos and minimizing hand-offs. While this may seem easy on paper, it is not so simple to execute without strong support from the organization.

In its purest form, DevOps is an outcome-driven culture of practices that supports the agile movement. Its core tenet is “culture first”, a mindset of working towards shared goals, versioning, automation, measurement, and improvement. Yes…

Chatbot, also known as “conversational agent”, is a trending technology. Chatbots are changing the business landscape. Its emergence in the enterprise has several implications that require some thought. Building a bot is not a hard task; with the rise of many platforms, it’s now easier than ever to develop and deploy one. The challenge with chatbots lies in delivering a good user experience, and they only present opportunities if done right. But, designing a conversation that meets consumer needs and returns real business value requires a nuanced strategy and in-depth considerations. The experience you are creating for your clients is…

The objective of any API is to meet the business’s goals in mind. Complicated as it may sound, building an API is easy! Where the challenge lies is in developing the right API that does precisely what the business need by following the principle of good design where APIs need to be consistent to be easily consumable. APIs can unlock data, increase agility, feed innovation, and speed time-to-market.

Figure 1: API Implementation for Entrepreneurs

This is the last in a series of three posts on API Lifecycle and Governance in the Enterprise.

  • Part 1: Plan
  • Part 2: Design
  • Part 3: Build & Deployment

This final post…

The API Economy is helping companies transform and realize opportunities that were never obtainable before the emergence of the cloud. The cloud is a game-changer and disrupts most companies, both from within and from new market players, using application programming interfaces (APIs). Thus, the proliferation of API-related technologies is shaping the way businesses interact with each other by offering new capabilities. APIs are adding an essential layer of agility which help to sustain the flexibility required to acquire more clients or partners, by sharing data and grow their business. An API management solution is now imperative for any company, and…

As the saying goes, “Bad governance is like bad design; it makes life harder”. With that in mind, we opt for a design-first approach. Thus, choosing the right API strategy is directly related to the ability to attract the right people, have the correct process in place, and deploy the right technology to align with the company’s strategy.

Figure 1: Balancing act between people, process and technology

API (Application Programming Interface) Lifecycle and Governance has the scope of an API Management platform architecture overview or a high-level design. The architecture team built it with input from the product subject matter experts (SMEs) and IT specialists for technical accuracy and…

Serverless (Functions-as-a-Service) computing is the next step in cloud evolution.

Figure 1: OpenWhisk Abstract Architecture Diagram. Image credit: Apache OpenWhisk™.

This blog is co-authored with Enrique (Ike) Relucio as part of our IBM Garage Engagements. Developing a single application is easy, but how do you go about showing extensible use of cloud-native features with multiple functions? We wanted to show a bit more than the traditional HelloWorld.

In recent years, the conversations have been predominantly on microservices. We have since built a great deal of architecture supporting the transformation to Cloud. Serverless is the next step in cloud evolution. With regards to Serverless, there are four concepts that you need to understand as an architect or developer: packages, actions, rules…

Ernese Norelus

Ernese is responsible for providing technical oversight to Cloud client projects!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store