Articles

Convenience is the key take away from AWS and Azure, because out of the box, they give you all the stuff you need to get started with your application development. However, creating your own cloud doesn’t need to be that difficult. If you create your own cloud you’ll also get rid of dozens of lockin technologies, such as Azure Functions, Lambda Functions, Cosmos DB, etc. These « features » provides you with few necessities besides the usual lockin. An acquaintance of me once compared these features to « the heroin marketing model, where the first doze is always free. »

If you want to create your own cloud, you’ll need the following features to get started.

Source de l’article sur DZONE

As more organizations move to establish DevOps techniques into their Software Development Life Cycle, the need of security becomes even more evident when so much application development is going on. But…

Security and DevOps Aren’t Natural Companions

The idea of security in DevOps or DevSecOps doesn’t go very well with the classic DevOps process that insists on continuous integration, delivery, and deployment. When at production you’re constantly releasing smaller bits of your code and application using the DevOps pipeline, introducing security to DevOps can slow down the process significantly. You can’t just pass that through a security team that takes several weeks bringing the new release out to production. 

Source de l’article sur DZONE

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

It’s not controversial to say that low-code has become a trend in the development of turnkey solutions for business. However, low-code is not traditionally the first choice for developing systems that handle complex business tasks. One of the main drawbacks associated with low-code development is the limited functionality of applications created. Often platforms do not provide an easy way to add custom code.

In this article, we will discuss if a low-code platform could be flexible enough to describe the logic of really sophisticated business processes.

Source de l’article sur DZONE

In a post published on our blog earlier this year, we described some of the decision-making that went into the design and architecture of Snuba, the primary storage and query service for Sentry’s event data. This project started out of necessity; months earlier, we discovered that the time and effort required to continuously scale our existing PostgreSQL-based solution for indexing event data was becoming an unsustainable burden.

Sentry’s growth led to increased write and read load on our databases, and, even after countless rounds of query and index optimizations, we felt that our databases were always a hair’s breadth from the next performance tipping point or query planner meltdown. Increased write load also led to increased storage requirements (if you’re doing more writes, you’re going to need more places to put them), and we were running what felt like an inordinate number of servers with a lot of disks for the data they were responsible for storing. We knew that something had to change.

Source de l’article sur DZONE

Managing a remote engineering team may not have topped your list of skills to acquire in 2020. However, the global pandemic made other plans for us this year. Remote work is now the new norm for software organizations, which is sending engineering managers scrambling to figure out what works best for communicating, collaborating, and coordinating from home. 

As luck would have it, I’ve become something of an expert at managing remote employees. My experience began in the early days of Bugsnag when my cofounder and I needed to hire engineers for our fledgling company. As San Francisco transplants, we had many roles to fill and wanted to take advantage of our networks back in the UK. In the end, we decided to build our company with an ocean and an eight-hour time difference between two offices.

Source de l’article sur DZONE

Finding a piece of software for creating a quick prototype of your future application may seem like a trivial task. But software prototypes are created by different people for different reasons. It could be a business analyst trying to communicate her vision to a designer, a marketer working on a website with a web dev, or a project manager demonstrating a future mobile app to a client.

Since people use wireframing tools for different purposes, it would be nice to know which tool would be your best bet for your specific situation.

Source de l’article sur DZone (Agile)