Articles

Serverless vs. Microservices Architecture: Is this the Future of Business Computing?

,

Serverless computing, which is commonly referred to as just Serverless, is a promising cloud-based technology model that has emerged on the app development and software architecture horizon in recent years. Trying to avail themselves of the huge serverless framework potential, many big-time market players have been quick to jump on the cloud services bandwagon. Such software giants like Google, Microsoft, IBM, and Amazon already offer the customers to migrate all the local business operational efficiencies to be hosted on their flagship serverless platforms like AWS Lambda and Azure Functions.   

Simply put, serverless architecture is an event- and request-driven tech solution allowing application developers to create actionable working environments in the cloud that have all the necessary computational resources needed for a smooth coding flow. This framework comes in handy especially when time is an issue and the tasks assigned are quite resource-intensive.

Source de l’article sur DZONE

/par

The Service Mesh in the Microservices World

,

The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.

The Problem

The majority of software companies are moving from Monolithic architecture to Microservices architecture, and Microservices architecture is taking over the software industry day-by-day. While monolithic architecture has many benefits, it also has so many shortcomings when catering to modern software development needs. With those shortcomings of monolithic architecture, it is very difficult to meet the demand of the modern-world software requirements and as a result, microservices architecture is taking control of the software development aggressively. The Microservices architecture enables us to deploy our applications more frequently, independently, and reliably meeting modern-day software application development requirements.

Source de l’article sur DZONE

/par

Event Sourcing in .NET Core: A Gentle Introduction

,

Event sourcing, aka "the great myth". I’ve been thinking about writing a series of articles about this for a while, and now it’s time to put my hands back on the keyboard. 

I thought that with this long period of confinement at least I could have had more time to write some nice articles, but it turns out the reality has been slightly different so far.

Source de l’article sur DZONE

/par

How Database B-Tree Indexing Works

,

When we think about the performance of a database, indexing is the first thing that comes to the mind. Here, we are going to look into how database indexing works on a database. Please note that here, architectural details are described referenced to SQLite 2.x database architecture. You can find out the backend implementation of SQLite 2.5.0 with tests, which is relevant to this post from https://github.com/madushadhanushka/simple-sqlite.

Read how overall SQLite database architecture composed in this DZone article.

Source de l’article sur DZONE

/par

Enterprise Architecture – Building a Robust Business IT Landscape

,
Simple or ornate, the enterprise architecture forms the structure for IT.
“The goal of enterprise architecture is boundary-less information flow where all systems, IT and non-IT, interoperate.” – Allen Brown

Today, when technology has proven its necessity amongst almost all industry segments around the globe, digitalization seems to be having a great influence on enterprise architecture (EA). Businesses are expanding beyond enterprise limits and IT solutions are encompassing enterprise, clients, stakeholder, ecologies and more. At such times, it is tough to manage a traditional monolithic framework. Now is the time to have a process that offers enough space for planning and managing the entire digital wave.

You may also enjoy: Role of Enterprise Architecture in DevOps Adoption

With this concept in mind, around the 1960s began the start of enterprise architecture. Initiated by Professor Dewey Walker and taken forward by his student John Zachmann, enterprise architecture found its entry into the tech world. Somewhere in the 1980s, enterprises realized that they would need a perfect planning approach to match pace with the fast-growing technological web. That gave further impetus to enterprise architecture, to extend beyond mere IT, trying to encompass all important ingredients of the business. The focus area was large organizations who are already in the digitization mode and need to have a seamless integration of legacy apps and processes.

Source de l’article sur DZONE

/par

You Had Me at Microservices! Oh, No…

,

"Microservices," the way it stands, is becoming a must-have for a lot of enterprises. It is being touted as the main component if you are leading a digital transformation journey. System integrators are having a field day calling themselves microservices experts. At the end of the day, 90% of implementations are going to fail. Why?

Because microservices by themselves are not the silver bullet. It is excellent armor, but by no means the only piece that you need to convert your legacy monolith — which, by the way, has seen the business grow leaps and bounds — into a lean, modern microservices architecture which will make your digital transformation journey successful. It is going to ruin a lot of C-level reputations.

Source de l’article sur DZONE

/0 Commentaires/par

How Microservices and Fast Data Are Converging

,

Mark Brewer is CEO of Lightbend, the company known for bringing Reactive to JVM application development. With Strata Data Conference in New York, DZone caught up with Brewer to hear more about trends he is seeing around microservices in the enterprise, and to learn about the 2.0 version of Lightbend’s Fast Data platform.

As the company behind the Scala language, Lightbend was very early on making new abstractions for microservices and data-driven applications available to the broader JVM ecosystem. Talk us through that a little bit.

Source de l’article sur DZONE

/0 Commentaires/par

Choosing a Legacy Software Modernization Strategy

,

We’ve put together this article by talking to the people involved in software modernization projects (in leading positions) here at ObjectStyle. The goal is to help decision-makers choose an optimal software modernization strategy. The post covers some common use cases and approaches to legacy software redesign. It’s also centered primarily around enterprise software development because these are the kind of projects we do most of the time.

What Is Legacy Software

The term "legacy software" is usually applied to a software system that was written decades ago in an outdated programming language, using some no-longer-supported framework(s), according to dated design principles, and/or that is currently running in an increasingly unsupportable environment.

Source de l’article sur DZONE

/0 Commentaires/par

29 Top Tools for Building Microservices on All Levels

,

There are many great articles out there on microservices. For those who have been hiding under a rock about the controversial technique—or are new to the idea—this article simply aims to collate the top open source tools available in one handy place. Microservice architecture, or just microservices, is a highly scalable structural style for developing software systems. Such architecture can be used for enterprise applications for businesses, governments, schools, and charities, etc. It is quite the opposite of the legacy-style monolithic architecture that focuses on a single unit application.

Microservices are small, independent, and unique. And the architecture can be complex in both construction and maintenance. Microservices communicate with each other to serve business goals utilizing synchronous protocols, HTTP/REST or asynchronous protocols. HTTP/REST or AMQP are examples of collaborating services that implement functions related to one another to work as efficiently as possible.

Source de l’article sur DZONE

/0 Commentaires/par