Skip to main content

Posts

Take Your Startup To The Next Level

Image
 So, you started a business. You had a great idea, and you did what it took to make that idea a reality. So, you started a business. You had a great idea, and you did what it took to make that idea a reality. You poured heart and soul into getting your business off the ground—from late nights to early mornings, you were determined to make it happen, whatever the cost. And now, your hard work has paid off. You’ve trademarked your name and patented your concept, you’ve hired, you’ve gotten funding, maybe you’ve even been in production for a few years now. Now, what comes next? If you’re ready to take your startup to the next level, it may be time to reevaluate some of your internal processes and prepare for growth. And if you’re really ready to join the big leagues, bringing in an expert partner is the way to do that. Here are the top three ways bringing on an expert IT partner can take your startup to the next level: #1. Experience When you bring on an outside IT consultant, you’re able

After Automation: What Comes Next?

Image
Digital transformation isn’t a fix-it-and-forget-it operation. Once you’ve transformed your processes, here’s what comes next. So, you made the jump, and transformed your IT systems with the most efficient processes available. Your legacy systems are gone, or all grown up with new and powerful software, innovative technology has been implemented throughout your organization, and efficiency and productivity maximized across the board. From automation to AI, the digital transformation is complete, and your system is prepared for whatever the future holds. As you survey the results of your time, effort, and innovation, you might be wondering… Now what? Digital transformation isn’t a fix-it-and-forget-it operation. Once you’ve transformed your processes, here’s what comes next: Looking Behind As you bask in the glow of your newly-minted modernized IT systems and software, take a moment to remember the last time you did this. Maybe it was ten years ago, but all those legacy systems that you

Java Persistence Done Right

Image
When it comes to accessing relational databases with Java, people usually think of two options When it comes to accessing relational databases with Java, people usually think of two options: 1. SQL (Structured Query Language) 2. ORM (Object Relational Mapping) Because the usage of SQL with the Java API JDBC (Java Database Connectivity) is painful and error-prone the first choice is usually an ORM like JPA/Hibernate. ORM Let’s have a look at the definition of ORM on Wikipedia : Object-relational mapping (ORM, O/RM, and O/R mapping tool) in computer science is a programming technique for converting data between incompatible type systems using object-oriented programming languages. This creates, in effect, a “virtual object database” that can be used from within the programming language. The idea behind a ORM framework is to hide the database access from the user. Another goal is to introduce capability to the database access layer that is do not exits in a relational database like inheri

Five Ways to Tell It's Time to Break Up with Your Legacy System

Image
When it comes to business operations, it’s easy to get comfortable in the status quo. When it comes to business operations, it’s easy to get comfortable in the status quo. Change seems daunting, especially in the context of legacy software. But often, just because a relationship is comfortable, doesn’t mean it’s what’s best for your enterprise in the long term. Here are a few reasons why it may be time to break up with your legacy system: 1. Security Issues Any enterprise worth its salt takes security seriously. Outdated software is one of the best ways hackers exploit their victims. There are thousands of industrial malware programs designed to target your systems in order to harvest you and your customers’ data, including sensitive financial information. Many malware programs can lurk for months (even years) harvesting information undetected. Here are several examples of how attackers focus on legacy gaps alone. 2. Reduced Performance In many cases, company productivity can only be a

Java 16 Records with JPA and jOOQ

Image
The new Java version 16 includes a new feature: Records Java Records The new Java version 16 includes a new feature: Records https://openjdk.java.net/jeps/395 “Enhance the Java programming language with records , which are classes that act as transparent carriers for immutable data. Records can be thought of as nominal tuples.” Let’s try Java records with JPA and jOOQ. JPA Constructor Expression One way to use projection in JPA queries is using the constructor expression. The name constructor expression implies that the constructor is called with the fields from the projection. select new com.demo.dto.EmployeeDTO(e.name, e.department.name) from Employee e In the example we have a DTO called EmployeeDTO and the constructor takes two Strings as parameters. With Java before Java 16 we would create a class like this: public final class EmployeeDTO { private final String employeeName; private final String departmentName; pu

You May Not Need JavaScript

Image
Simon Martinelli’s talk about a recent ERP modernization project using Vaadin and jOOQ at DawsCon is online. Simon Martinelli’s talk about a recent ERP modernization project using Vaadin  and jOOQ at DawsCon is online:

Making the Case for Digital Renovation

Image
Are you working for an enterprise that utilizes outdated software? Are you working for an enterprise that utilizes outdated software? Old software, or legacy systems, pose threats to businesses looking to streamline processes, cut costs, and stay innovative. While users resist change and implementing new software is neither easy nor always feasible, opting for digital renovation can bridge legacy systems to modern demands. Legacy Systems Cost Your Business Too Much Money In making a case for software modernization, the most compelling reason tends to be the money saved by reducing excess labor costs and other inefficiencies incited by legacy systems. Less efficient to maintain Due to the grandiose size of legacy systems’ codebases, updating these systems can engender various problems, rendering the process both laborious and lengthy when done correctly. Additionally, the infrastructure of old software is more challenging to maintain and becomes increasingly challenging as the software