↳
Continuous Integration is a software development practice where members of a team integrate their work frequently, usually, each person integrates at least daily leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. Continuous Delivery is a process, where code changes are automatically built, tested, and prepared for a release to production. Continuous Deployment - is an approach of releasing software on the production servers continuously in an automated fashion. Less
↳
Well, the question is a little vague, and a tad misleading first off I'm not really sure what CIDR notation has to do with continuous deployments in this context. So I will assume it's asking for both. CIDR is a notation used to express a variety of network conditions, using convenient slash notation. A class A/B/C would be represented with either 10.x.x.x./8 - a , 172.168.x.x/16, or 192.168.1.x/24. You can set a range of IPs or Network Ranges using slash notation to split networks even further, so you could sub-class a C subnet into a small subset, i.e. 192.168.1.3/32 would denote a single address, The conversion - Subtracting the number of network bits from 32. Raise 2 to that power and subtract 2 for the network and broadcast addresses. For example, a /24 network has 232-24 - 2 addresses available for host assignment. CI/CD is Continuous Integration and Delivery - simply put this is how the code lifecycle follows thru from maturity. It starts in the repo, and it gets run through a gauntlet through something like Jenkins, Travis or CircleCI. Until it's finally merged and committed for deployment. This can refer to any component before the delivery, and up to the deployment of the product. Less
↳
RDBMS works with structured data, NoSQL works semi or unstructured work RDBMS - vertically scalable, NoSQL - Horizontally Scalable RDBMS needs ACID compliance RDBMS tend to rely on expensive servers and storage, NoSQL DBs usually use cluster of commodity servers RDBMS's suffer from no horizontal scaling, NoSQL DBs solve high transaction laods but at the cost of data integrity and joins Less
↳
With a new network being connected to the Internet every 30 minutes the Internet was faced with two critical problems * Running out of IP v4 addresses * Running out of capacity in the global routing tables In the original IP addressing scheme, we have Class A,B, C that has /8, /16, /24. Let’s say I need 10 IPs so I have to go for /24 which means I’m going to waste 154 IPs. Classless Inter-Domain Routing (CIDR) is a replacement for the old process of assigning Class A, B and C addresses with a generalized network "prefix". Instead of being limited to network identifiers (or "prefixes") of 8, 16 or 24 bits, CIDR currently uses prefixes anywhere from 13 to 27 bits. CIDR is a new addressing scheme for the Internet which allows for more efficient allocation of IP addresses than the old Class A, B, and C address scheme. (/8, /16, /24) Less
↳
So that can be implemented by making the size of the random number generation equal to the size of the array and then print all the numbers at the indexes generated by the function. Is this right? Less
↳
List list = new ArrayList(); for(int i = 1; i <= 100; i++) list.add(i); Collections.shuffle(list); Less
↳
Not really, interesting meaningful work matters to me.
↳
Outlined a couple of occurrences