Microservices define the latest iteration of a service-oriented architecture, under which applications are not written as a monolith but are built by joining discreet components — bits of functionality, called services — via application programming interfaces (APIs).
Among the advantages microservice architectures provide are the ability to iterate more quickly, by having teams work on these individual application components, speeding both bug fixes and the introduction of new features. These microservices are deployed via containers, which can be taken down from an application, amended, and plugged back in without causing the entire application to come down.
While the benefits of microservices are clear, having so many small pieces of functionality used to compile applications creates a security issue. The more services you run, the more surface area hackers can exploit. Microservices also create problems because often, organizations don’t know who created a service, or what will happen to their application if the service changes before they are aware of the change. Then there is the enormous issue of managing so many small, moving pieces.
It’s safe to say that microservices architecture is no longer an emerging new trend, but a mainstream software development strategy. Microservices aren’t just ideal for developing new applications, but are also optimal when modernizing legacy applications. Writing functionality into bite-sized, reusable components is more efficient and speeds up development. It delivers code that meshes well … continue reading
The work on a microservices project is always stressful. Such projects introduce larger data sets, faster update rates, more requests, more failures, more latency challenges, more service interdependencies, more developers, more documentation, more servers, more networks, more databases. Yet, all that doesn’t mean you should avoid microsevices-based projects. The right organization of your team … continue reading
Have you thought about what your future looks like when you’re managing hundreds of containers and microservices that make up a single version of your software solution? Let’s just say, you’re going to need more than an Excel spreadsheet. Containers and microservices are game-changers in terms of how we develop and deliver software. In the … continue reading
The rise of microservices and serverless applications has enabled developers to build apps at scale and with less complexity at lower costs. But these new modern apps also come with a new set of issues and problems developers have to be concerned about. Data Theorem today announced new automated API solutions aimed at addressing threats … continue reading
The Apache Software Foundation has announced that Apache ServiceComb is graduating from the Apache Incubator and is headed for Top-Level status. Apache ServiceComb is an open-source microservices software framework for building and managing microservices. “We are very proud that ServiceComb has arrived at this important milestone,” said Willem Jiang, vice president of Apache ServiceComb. “ServiceComb … continue reading
Know your apps, know your workloads, know your team. In the third installment of this occasional series on cloud migration, Don Boulia, GM of IBM Cloud Developer Services, and guest Chris Condo, principal analyst at Forrester Research, discuss how cloud-native development teams can find more success through innovation, automation, and culture shifts. How can cloud-native … continue reading
The term ‘cloud native’ is responsible for significant confusion in conversations about contemporary application development because of a lack of clarity about its meaning. For example, contemporary usage of the term often equates it with applications that are optimized for cloud computing infrastructures. Another use of the term equate it with cloud-based applications that are … continue reading
The beginning of October marks the start of Halloween season, but one thing you don’t want to frighten or scare your users with is your application. There are many benefits to moving your monolithic applications to microservices, but it can be easier said than done. Inability to manage services, set good service boundaries and provide … continue reading
The role of APM has traditionally been to flag issues in code that affect performance. To resolve those issues, it has been necessary to understand all the spaghetti code of a monolithic application – written by multiple developers who often do not have an overarching view of the entire application – and then deconstruct that … continue reading
If you’re not doing static code analysis (aka static analysis), now is the time to start. Delivering code faster has dubious value if the quality degrades as development cycles shrink. On the other hand, if you’re not doing static code analysis, you’re not alone. Despite the mature age of the tool category, not a lot … continue reading
Enterprises of all sizes are adopting the microservice approach, but not everyone is adopting it correctly. According to Chase Aucoin, developer evangelist for AppDynamics, too often, businesses think if they move their monolith applications to microservices, their problems will just magically go away. However, once they start to move to microservices and realize their problems … continue reading
The way software is built is constantly changing to meet the ongoing pressure of getting to the market faster and keeping up with the competition. The software development industry has gone from waterfall to Agile, from agile to DevOps, from DevOps to DevSecOps, and from monolithic applications to microservices and containers. Today, a new approach … continue reading