Search Results

A significant factor is tooling used by the team and the proficiency with which developers use the tools. The concept of refactoring was originally developed in the Smalltalk context, and there were a …

You've already mentioned the options and their pros/cons. You might also want to look at commercially available options for comparison. In any case, the decision should likely be one of economy - how …

I would suggest combining jobs that should be run on the same schedule (hourly, twice daily etc.) but should not run in parallel into shell scripts which execute them in sequence, so if one job runs a …

This sounds like a better approach would be to implement a list of business rules with validity date limits, section applicability, ordering key. Then for every section, you execute the applicable rul …

Design an algorithm An algorithm can be designed and analysed for theoretical correctness without committing to a specific technology. …

First of all, this sounds like a set of complicated and possibly inconsistent business rules, it's hard to implement such rules in software. The only thing you can be certain of is that someone's inte …

You're somewhat misinterpreting the Java documentation. It merely states that file locks may have somewhat different semantics on different operating systems and file systems. In general, if you treat …

You should consider internal behavior and UX separately. Internally, an attempt to start a second navigation while there is an ongoing one should be handled just like you would handle other invalid na …

If you can do only 50 requests per minute you'll never be able to provide individual charts per user if you use up your precious API requests to serve one user request. Your only chance is to gather h …

As a first step, this is a reasonable approach (I can't vouch for DDD or Clean Architecture, just common sense and experience). However, in the long run you might want to keep the connection between t …

Any queueing service supporting multiple consumers will do. REDIS lists are suitable for this, as are the various message brokers such as RabbitMQ or ActiveMQ. You need to consider how you handle cras …

The classic approach to handling sluggish external accesses is caching. You might have heard of that :-) Caching does not help in every case (for example, if you access a resource for the first time, …

This approach looks reasonable, and incidentally I have done something similar to store polymorphic values in a relational database. The storage overhead for NULL columns is often negligible, and the …

Your examples are both in the area of interfaces to systems that are not under your control, which is different from the interfaces between components that you control and where you can ensure that th …

The simple solution of implementing generateHTML() and overriding it in subclasses is indeed a common object oriented approach, but as noticed, it puts unrelated logic or functionality into business o …