| Author | Message | ||
Twotown Side Hero Username: Twotown Post Number: 7093 Registered: 09-2016 Posted From: 207.244.66.70 Rating: N/A |
final gaa em telcharu... | ||
Stalker Comedian Username: Stalker Post Number: 1687 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
ala cheppu annai, anosaramga burra paaduchesukuntunna kada  | ||
Stalker Comedian Username: Stalker Post Number: 1686 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
we could do something like this I guess 1. deploy kubernetes cluster and docker on bare metal 2. deploy openstack kolla project which is a container based which would give us vm instances 3. install kubernetes cluster on top of these vm workers and run your apps there.. this is like running kubernetes on kubernetes... I guess LA bro you guys currently running step 2 and 3, in that case I wouldnt call kubernetes providing the vm resources... it is your cloud formation API's that are providing you the infrastructure stack that internally would use openstack API's to deploy vm instances, provision them, install docker and resgiter/install kubernetes on those VM's... its a complete stack deployment...not just running some application container on top of k8s cluster | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 9002 Registered: 09-2012 Posted From: 12.10.219.226 Rating: N/A |
Mestaru, VMs i mean JVMs, not the VMs provided by IaaS sorry for thew confusion Physical Hardware -> OS -> VMs in IaaS -> PaaS ( Docker, Kubernetes containers) -> PODs -> JVMs/others -> Applications | ||
Stalker Comedian Username: Stalker Post Number: 1685 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
confusing.. how come a kubernetes cluster provide a VM for you annai? thats the job of IAAS...in your case an ec2 instance...aa instances anni IAAS provision chesi istaadi...vaatini kubernetes ki register cheste any application container that you deploy thereafter would be managed by kubernetes... memu as part of IAAS on premise DC/OS(mesos/kubernetes) cluster ni bring up sestimi...daani meeda platform services like logging(elk) etc is platform bagotham... basically initially we(IAAS) deploy the kubernetes cluster..PAAS ollu service accounts, groups, AD accounts create sesukuni kubernetes cluster ni manage chesukuntaaru...vaalla pindakoodadu...they shouldnt be managing the k8s cluster...they should be managing the platform services...anni roles mixup ayipothunnayi vaalla pindakoodu...anthe vaallu cheste inka memeti cheyyali vaalla pindakoodu  anyway back to topic seyyandi roles gurinchi endukule | ||
Stalker Comedian Username: Stalker Post Number: 1684 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
yep IAAS cloud  | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 9000 Registered: 09-2012 Posted From: 12.10.219.226 Rating: N/A |
Physical Hardware -> OS -> IaaS -> PaaS ( Docker, Kubernetes containers) -> PODs -> VMs -> Applications | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 8999 Registered: 09-2012 Posted From: 12.10.219.226 Rating: N/A |
Annai, when we submit the application specs to PaaS team, we mention min and Max vms, so once we deploy once it will auto scale, we need not do any thing. in case one dies other gets triggered Regaring WARs and EARs i was specific to our migration. So it is not genraric, as ours is J2EE application running on websphere | ||
Gatti_gunde Megastar Username: Gatti_gunde Post Number: 21886 Registered: 02-2010 Posted From: 204.194.77.3 Rating: N/A |
meeru devops aaa Boob annai ni kindhesi thanthe DB set aithadhi | ||
Stalker Comedian Username: Stalker Post Number: 1682 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
idi ardamkaale annai why would you care about vm instances? ec2 instances kada avi meerenduku adugutaaru...infrastructure stack munde set ayyi untaadi with these many ec2 instances and those instances should be registered to the kubernetes cluster and auto scaling groups... as an application owner, you will ask fore number of "cores" for your app and once you have them you run your app... war's, ear's ardamkaaledu  ...java meeda eppudu pani cheyaledu annai...bebbebe there....in kubernetes cluster I thought all you need are containers...wars kooda deploy cheyyochaa hmm... anyways thank you annai for the detailed info...appreciate it | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 8992 Registered: 09-2012 Posted From: 12.10.219.226 Rating: N/A |
Abba chaa..., Nee question lo vetakaram baaga undi kaani, Vinu On PaaS , as application owner, - you are not going to manage docker and Kubernetes clusters - It is the PaaS Sys Admin team to create the echo system like clusters and containers with desired software footprint (like jboss, nodejs , mongodb etc) - Application team to take existing MVC monotlithic app that runs on traditional app servers , comply with target environment, split the EARs to WARs - Application team using the PaaS console create application vm instances, deploy WARs , depending on preset configuration max instances gets replicated deploytime - before deploying in PaaS, we need to establish integration with existing interfaces, SSO, SSL certs Chala Boss Inka Emayina kavala... | ||
Stalker Comedian Username: Stalker Post Number: 1681 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
migration ante em seseru annai koddiga vivarimpudi services anni oka bash script lo etti environment antha set chesi bash script run sestira docker command lo or inka emina migration steps untaaya...koddiga seppu annai inipedata | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 8990 Registered: 09-2012 Posted From: 12.10.219.226 Rating: N/A |
we have recently and successfully migrated monolithic apps 28 with Docker and kubernetes with jboss (PaaS) with traditional DB2 on backend running fine with no performance issues. however we have divided EARs into individual wars and deployed But ideally this setup is good for micro services | ||
Stalker Comedian Username: Stalker Post Number: 1678 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
this way it has other disadvantages and thats precisely why people opt for microservices....ippudu nee app provides two services x & y anukundaam and x service get more users... incase you built your app as one big gaint container and scale it horizontally then the resources utilized for y service are wasted for some or no users at all... | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2143 Registered: 04-2016 Posted From: 73.241.241.99 Rating: N/A |
here we are talking about two different things...if you are worried about foot print...you can still run your monolithic application in Docker containers...it doesn't have to be micro services | ||
Stalker Comedian Username: Stalker Post Number: 1677 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
containers with a minuscule OS | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2142 Registered: 04-2016 Posted From: 73.241.241.99 Rating: N/A |
Where do you think the micro services are running on? | ||
Stalker Comedian Username: Stalker Post Number: 1676 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
no nuvvu cheppedi vertical scaling where you increase/decrease the resources...but naan seppedi hortizontal scaling...how do you make sure you run more copies of the app? example sebuta soodu annai..oka enterprise application ni monolitic ga build chesav anuko...danni oka vm lo estaav...adi edo port meedi service ni expose chestaadi...now if you want to scale the app, you need to build another VM with app deployed in it and exposed on the same port...ila N number of vm's ni oka load balancer kinda padestaav so that you have one endpoint that loadlabalances these VM's which are running the copy of the monolithic app... ikkada scale ante app footprint + VM footprint(which is complete full blown OS)...idi enduku ekkuva scale cheyalevu antunna ante...physical host capacity is limited kada antha antha footprint OS ki pothe actual application copies limited ayipothayi ga adhe microservice level ayuthe OS footprint takkuva kabatti you can scale them more ani naa uddesam of africa.. | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2141 Registered: 04-2016 Posted From: 73.241.241.99 Rating: N/A |
scaling antey ney increasing/decreasing the footprint kadha..unless I am missing something | ||
Just4fun Legend Username: Just4fun Post Number: 35803 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
SOA antene bunch of web services follow some pattern, each service maybe loosely coupled but when you deploy them to server all has to follow server rules so you cann't scale them indicatively paiga server/infra maintenance bokka | ||
Stalker Comedian Username: Stalker Post Number: 1675 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
application may be independent but mostly monolythic applications are tied to the host...inorder to maintain them you need to consider the vm footprint too kada... | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2140 Registered: 04-2016 Posted From: 144.49.132.22 Rating: N/A |
??...if you have independent components in your application...you can scale them individually...how is it tied to foot print? | ||
Stalker Comedian Username: Stalker Post Number: 1674 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
you "can" scale but depends on the footprint...the bigger the footprint, bigger the challenge to scale.. so break them to micro level anede bg | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2139 Registered: 04-2016 Posted From: 144.49.132.22 Rating: N/A |
I think j4u is talking about dynamic scaling...when your traffic patterns are already accounted for...you can design once and forget about it | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2138 Registered: 04-2016 Posted From: 144.49.132.22 Rating: |
I think you are drinking too much Microservices Koolaid...I agree that it's very use ful for scaling/de-coupling business logic anthey if you use SOA you cannot scale anedhi wrong argument...Microservices vall deployment/maintenance/colloboration between teams easy avutundhi Lets say you have a monolithic application talking to some backend...you can scale them separately | ||
Just4fun Legend Username: Just4fun Post Number: 35802 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
umma chinna discount sale pedite enni sites crash avvaledu avanni Scalability issue ee. servers handle cheyalevu abnormal traffic ni | ||
Just4fun Legend Username: Just4fun Post Number: 35801 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
i doubt it uncle. SOA maintain cheyali ante total ESB tool maintain cheyali. even if you wants to make small change for 1 service related services also get effected. Inka oka service kosam server scale up cheyali ante not possible in SOA related applications. Already few ctos videos ettaru SOA ki future kastam ani | ||
Bharat Side Hero Username: Bharat Post Number: 4056 Registered: 06-2015 Posted From: 149.168.240.7 Rating: N/A |
Scalability is really overrated. For most of the enterprise applications, the user numbers and hardware requirements can be accurately guessed beforehand. Not every application is a Netflix or Google. Cloud is definitely the future but the pricing will have to come down. | ||
Stalker Comedian Username: Stalker Post Number: 1673 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
super, thanks bro | ||
Stalker Comedian Username: Stalker Post Number: 1672 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
this is still fine with dcos/kubernetes in combination with elk | ||
Just4fun Legend Username: Just4fun Post Number: 35800 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
I don't know anyone right now annai, naaku teliste or nenu train aite willl let you know. | ||
Gandhiguevara Legend Username: Gandhiguevara Post Number: 64297 Registered: 10-2009 Posted From: 175.101.105.36 Rating: N/A |
wrong...SOA ekkadikee podhu...denikundaalsindhi daanikuntundhi....ivi rendoo 'service-based architectures' lo 2 different patterns | ||
Just4fun Legend Username: Just4fun Post Number: 35799 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
make sense. already small application and small team so need to move to serverless unless you wants to save infra cost. only -ve i see is debugging/troubleshooting with microservices. rest all li8 | ||
Stalker Comedian Username: Stalker Post Number: 1671 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
ivemi reasons baale...ante simple hello world application by aasha infotech build cheste micrservices vaddu annattu undi...none of the work we do generally are not so limited in scope kada...scale undali anukuntaadu evadina, hopeful of business growth kada.. | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 8977 Registered: 09-2012 Posted From: 12.10.219.226 Rating: N/A |
JAXenter: What is the biggest challenge of microservices? Daniel Bryant: One of the primary challenges is not getting caught in the hype. Resist the temptation to build everything as a microservice — it is simply an architectural style, and like all such styles, has strengths and weaknesses. Another primary challenge includes testing — microservice systems inherently have more dependencies that must be managed, and testing the interactions between services can be challenging. This is why I have been working with the SpectoLabs team on the development of various tools to support the testing of microservice-based systems | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 8976 Registered: 09-2012 Posted From: 12.10.219.226 Rating: N/A |
Hope you understand what i was trying to say JAXenter: When should you not use microservices? Daniel Bryant: I get asked this question quite a lot, and it is difficult to give a definitive answer. However, situations where microservices may not be beneficial include: – Working with a simple application domain – Developing software with a small number of people in the team – No problem/solution or product/market fit e.g. you are a startup that is still exploring your business domain and how to make money – When the organisation is not embracing DevOps principles (i.e. see Martin Fowler’s MicroservicePrequisites article). | ||
Stalker Comedian Username: Stalker Post Number: 1670 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
deeni ardam concur salesforce connectors meeda pani chestiva annai naaku mulesoft lo oka support resource kaavali...evaranna unte cheppu...TIA | ||
Just4fun Legend Username: Just4fun Post Number: 35798 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
simple more scalable, less maintenance, less resources and cost saving. All are valid points. Why not micro /nano? My self I am working in conventional monolithic architecture and convinced with serverless architecture. I heard Netflix completely moved to microservices and no on premises infra | ||
Last_avataar Side Hero Username: Last_avataar Post Number: 8975 Registered: 09-2012 Posted From: 12.10.219.226 Rating: |
warni - pigugu biyyaniki okate mantram aa ? we select the technologies based on the system functions and needs why would we develop micro services or nano services for every thing ? There are many systems that run behind web / mobile interface which could be built on many technologies oka technology nerchukunte adi ekkada fit avutundo Architecture lo, kooda understand chesukunte.... great value intundi Good Luck | ||
Stalker Comedian Username: Stalker Post Number: 1669 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
deeni meeda inputs ivvu annai...emaina articles raaste share cheyu | ||
Just4fun Legend Username: Just4fun Post Number: 35797 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
yes but not mule | ||
Just4fun Legend Username: Just4fun Post Number: 35796 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
The word 'serverless' doesn't stand for No Servers. Serverless computing is an event driven application design and deployment paradigm where all the computing resources are provided as scalable cloud services | ||
Stalker Comedian Username: Stalker Post Number: 1668 Registered: 08-2012 Posted From: 208.78.142.232 Rating: N/A |
j4u bro, are you working in mule or esb space? | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2137 Registered: 04-2016 Posted From: 73.241.241.99 Rating: N/A |
to the end user he is not deploying any EC2 or any other instances to run his application...user only specifies the script that need be run and when it needs to be run | ||
Bithiri_bathi Side Hero Username: Bithiri_bathi Post Number: 2136 Registered: 04-2016 Posted From: 73.241.241.99 Rating: N/A |
Docker - Light weight VM (with out virtualization overhead) Microservices - nothing magical...inthaka mundhu one big application use to handle all the REST APIs (monolithic application), ippudu Micro/nano ani cheppi..you split all the services into multiple vertical services (based on your business logic) You don't need cloud to implement micro services...you can quickly build micro services using Python Flask | ||
Wellsfargo Side Hero Username: Wellsfargo Post Number: 8011 Registered: 06-2012 Posted From: 124.123.174.127 Rating: N/A |
Lamda serverless enti... oka server edchindi kada aws vadidi... | ||
Twotown Side Hero Username: Twotown Post Number: 7088 Registered: 09-2016 Posted From: 207.244.66.70 Rating: N/A |
edhi tappa edaina nerchukondi ..edhe baatamline..  | ||
Just4fun Legend Username: Just4fun Post Number: 35795 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
bottom line idE super. so for serverless docker is useless. both are Javascript languages kada | ||
Platypus Side Hero Username: Platypus Post Number: 6634 Registered: 01-2008 Posted From: 89.192.131.100 Rating: N/A |
At every point. TCO and ROI drive everything including innovation.
Because if I were Microsoft, I believe that there is greater value in the long term to advise a cost effective option to the customer though I may lose out on consumption in the short term. (I don't speak for MS. Just my personal opinion) | ||
Andhravodu Moderator Username: Andhravodu Post Number: 11150 Registered: 07-2015 Rating: N/A |
at what point do the cost/benefit ratio kick in for serverless design? Small/medium systems ki work avutunda or do you need to go full blown in size? I mean if I was MS, why would I be promoting a lesser expensive version? I have to make my money somehow right? AWS competition koddi istunnaru ani anukonu | ||
Rgb Side Hero Username: Rgb Post Number: 4404 Registered: 06-2014 Posted From: 162.115.236.102 Rating: N/A |
Avi rendu Javascript kadha | ||
Just4fun Legend Username: Just4fun Post Number: 35794 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
idi kuda fadeout aipodi. Spring-Microservices required server..where as Lambda SERVERLESS. no maintenance at all. just oka developer unte chalu dev to prod anni vaade chusukuntadu | ||
Platypus Side Hero Username: Platypus Post Number: 6633 Registered: 01-2008 Posted From: 89.192.131.100 Rating: N/A |
AWS Lamda Google Cloud Functions Azure Functions Mark my words, this is where all the action is going to be. However, if you need stateful microservices, not sure if you can do it with Lambda. Let me pitch in Azure Service Fabric Having said that, if I were architecting a new system from scratch - I would try to design a stateless architecture so that I can go the serverless route and save big on my infra footprint. Docker is a container. You can put your microservice inside a docker container as well. In this case, you are responsible for the underlying hardware as well unless of course you use a managed container service such as Azure Container Service or AWS EC2 Containers. Node JS, Angular etc are the most commonly known frameworks in Java. | ||
Just4fun Legend Username: Just4fun Post Number: 35793 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
davier , lauda endo aa names.,. | ||
Enigmatic Comedian Username: Enigmatic Post Number: 1095 Registered: 11-2010 Posted From: 98.115.156.236 Rating: N/A |
java ayithe ee book chudandi https://www.amazon.com/Spring-Microservices-Rajesh-RV-ebook/ dp/B01FWFHVKE/ref=sr_1_2?ie=UTF8&qid=1499271977&sr=8-2&keywo rds=spring+microservices | ||
Ferrari Hero Username: Ferrari Post Number: 12333 Registered: 10-2008 Posted From: 192.158.48.90 Rating: N/A |
docker ante manam esukune davier ey kadha .. | ||
Just4fun Legend Username: Just4fun Post Number: 35792 Registered: 10-2007 Posted From: 204.235.114.164 Rating: N/A |
So I was doing little research over the weekend. I found out that SOA is going away slowly and future is Microservice architecture. The reasons for moving out of SOA are scalability, maintenance of ESBs, more resource required etc. Now for Microservices, lot of people talking about AWS Lambda. digged into Lambda.My understating is Lambda provides Faas(Functions as service). So it provided Micro/Nano services. Functions you can write in Java/.net/Python/Node js. Lot of developers using Node js don't know why. final ga to start to learn microservices AWS Lambda and Node js enough ? where does docker fit into this? Jai ho cloud ....future anta CLOUD ee. mule ledu sollu ledu |
