Buzzwords often give context to concepts that evolved and needed a good “tag” to facilitate dialogue. Microservices is a new “tag” that defines areas I have personally been discovering and using for some time now. Articles and conferences described something that I slowly realized I had been evolving in my own personal experience for the past few years.
Senior IT executive with over 18 years of experience in Healthcare, Pharmacy, Financial Services and Insurance sectors. Skilled strategist who blends deep technical expertise with an enterprising business sense to create competitive advantage.
Where is enterprise architecture in healthcareJon Cohn
Integration, interoperability, data quality, process automation analytics -- these ideas are simple to describe but can be quite hard to execute in today's business environments. The road to building information-driven businesses far from well-paved.
What does the future hold for BI, CRM, ERP and enterprise software in 2015? IT experts discuss which enterprise software trends will have the greatest impact on IT organizations in the coming year
The big data architecture dilemma for ci osJon Cohn
CIOs face an age-old dilemma in architecting for big data: Do I buy or build? New business problems, inadequate vendor solutions and myriad new technologies complicate the decision. Add to all that the ambiguity of the term, big data, and well ...
Senior IT executive with over 18 years of experience in Healthcare, Pharmacy, Financial Services and Insurance sectors. Skilled strategist who blends deep technical expertise with an enterprising business sense to create competitive advantage.
Where is enterprise architecture in healthcareJon Cohn
Integration, interoperability, data quality, process automation analytics -- these ideas are simple to describe but can be quite hard to execute in today's business environments. The road to building information-driven businesses far from well-paved.
What does the future hold for BI, CRM, ERP and enterprise software in 2015? IT experts discuss which enterprise software trends will have the greatest impact on IT organizations in the coming year
The big data architecture dilemma for ci osJon Cohn
CIOs face an age-old dilemma in architecting for big data: Do I buy or build? New business problems, inadequate vendor solutions and myriad new technologies complicate the decision. Add to all that the ambiguity of the term, big data, and well ...
Enterprise Architecture is an ongoing strategy, planning and management process to help Business and IT executives to align the business strategy with the execution of that strategy with IT.
In a corporate sense, innovation management is about quickly and effectively implementing your organization goals through the adoption of innovative ideas, products, processes and business models. Most organizations are beginning to realize that to drive business growth and maintain a competitive advantage, innovation needs to be discovered and implemented quickly and with care to ensure maximum value.
Can content management be used as an asset to boost productivity and collaboration?
Atos’ performance at the Olympic Games has proved the ideal challenge to improving the way we deliver world-beating business technology for our clients. This new Fast Track Guide on ECM is quick to read and formed from the very latest thinking. It describes how, in the economic climate, enterprise collaboration tools have been embraced by organizations looking to become leaner and more flexible to boost productivity and efficiency across an increasingly dispersed and mobile workforce.
Digital Businesses Need to Rethink Their Network StrategiesAbhishek Sood
This report from ZK Research explores why it’s critical that digital businesses rethink their network strategies and embrace a software-defined future. Access now to discover:
The challenges of traditional networks
Why SD-WANs are the foundation for new enterprise networks
How you can chart a path to the SD-WAN
Key criteria for evaluating SD-WAN solution providers
This issue of the Technology Forecast explores the future of enterprise applications and their role in creating a foundation for agility in an era of accelerating change.
State of Cloud 2016 - WGroup Industry ReportWGroup
Cloud technology is core to delivery of services in almost every industry, but its ongoing evolution means your organization needs to be flexible and agile enough to change with it. New services and applications appear daily, and cost structures are constantly changing. This special WGroup industry report, State of Cloud, will help you understand its rapid evolution so you can refine your IT strategy and fully leverage the power of today’s cloud in your organization.
This new world of technology presents an unprecedented opportunity for executives to enhance IT’s value across the enterprise. ReThink IT analyzes the five most disruptive trends in IT, and addresses the issues and challenges faced by today’s CIO and IT leaders. These disruptive trends point to a new role for IT and the CIO, and the fact that IT responsibilities have moved into the business makes the role of services integrator and advisor to the business the primary focus of the CIO.
Enterprise Architecture is an ongoing strategy, planning and management process to help Business and IT executives to align the business strategy with the execution of that strategy with IT.
In a corporate sense, innovation management is about quickly and effectively implementing your organization goals through the adoption of innovative ideas, products, processes and business models. Most organizations are beginning to realize that to drive business growth and maintain a competitive advantage, innovation needs to be discovered and implemented quickly and with care to ensure maximum value.
Can content management be used as an asset to boost productivity and collaboration?
Atos’ performance at the Olympic Games has proved the ideal challenge to improving the way we deliver world-beating business technology for our clients. This new Fast Track Guide on ECM is quick to read and formed from the very latest thinking. It describes how, in the economic climate, enterprise collaboration tools have been embraced by organizations looking to become leaner and more flexible to boost productivity and efficiency across an increasingly dispersed and mobile workforce.
Digital Businesses Need to Rethink Their Network StrategiesAbhishek Sood
This report from ZK Research explores why it’s critical that digital businesses rethink their network strategies and embrace a software-defined future. Access now to discover:
The challenges of traditional networks
Why SD-WANs are the foundation for new enterprise networks
How you can chart a path to the SD-WAN
Key criteria for evaluating SD-WAN solution providers
This issue of the Technology Forecast explores the future of enterprise applications and their role in creating a foundation for agility in an era of accelerating change.
State of Cloud 2016 - WGroup Industry ReportWGroup
Cloud technology is core to delivery of services in almost every industry, but its ongoing evolution means your organization needs to be flexible and agile enough to change with it. New services and applications appear daily, and cost structures are constantly changing. This special WGroup industry report, State of Cloud, will help you understand its rapid evolution so you can refine your IT strategy and fully leverage the power of today’s cloud in your organization.
This new world of technology presents an unprecedented opportunity for executives to enhance IT’s value across the enterprise. ReThink IT analyzes the five most disruptive trends in IT, and addresses the issues and challenges faced by today’s CIO and IT leaders. These disruptive trends point to a new role for IT and the CIO, and the fact that IT responsibilities have moved into the business makes the role of services integrator and advisor to the business the primary focus of the CIO.
Trade In ValueMost of the individual seller wants to get the best trade in value for their vehicles, and many of you wonder if the dealership quote is the best you can get out of it.
ExperiaSphere: Open-Source Management and Orchestration--Introductiontnolle
This presentation is an annotated set of tutorial slides on the ExperiaSphere(TM) model of open-source management and orchestration. It provides an overview of how to build on open-source tools like Linked USDL, OpenTOSCA, RTG, and OpenNMS to build the basis for management and orchestration for legacy networks, SDN, NFV, and the cloud.
The CLOUD. For techies - it is as real as an ashtray - to the non technical - it is invisible - can't be held in your hand or described - find out what all the chatter is about!
CPU and RAM costs continue to plummet. Multi-core systems are ubiquitous. Writing code is easier than it has ever been. Why, then, is it still so darn hard to make a scalable system?
Platforms and Microservices - Is There a Middle Ground for Engineers and Tech...Dialexa
Your technology strategy is the key to executing successful digital transformation. But if you talk to engineers and strategists, there are opposing views on the best way to leverage technology.
While engineers might push for a pure microservices architecture, strategists may take a step back and consider the long-term implications of that decision on the enterprise. Is there a middle ground?
Our own VP of Engineering, Samer Fallouh, and Head of Technology Strategy, Russell Villemez, discussed this topic to see if there was some middle ground to drive innovation more effectively.
Full write-up: https://by.dialexa.com/platforms-and-microservices-is-there-a-middle-ground-for-engineers-and-tech-strategists
How FinTech Innovator Razorpay Uses Open-Source Tracing And Observability to ...Dana Gardner
Transcript of a discussion on an open-source project, Hypertrace, and how it helps designers, builders, and testers of modern APIs gain visibility across their internal and third-party services.
In recent years, the need to manage digital assets has become critical - compelling organizations to focus more on how digital asset management (DAM) systems can be leveraged across the digital supply chain, rather than simply archived. DAMification employs DAM concepts and systems to automate, integrate and enhance workflows, processes and applications - all within an adaptable, technology-agnostic framework that utilizes best-of-breed solutions and supports positive business growth.
Service meshes are relatively new, extremely powerful and can be complex. There’s a lot of information out there on what a service mesh is and what it can do, but it’s a lot to sort through. Sometimes, it’s helpful to have a guide. If you’ve been asking questions like “What is a service mesh?” “Why would I use one?” “What benefits can it provide?” or “How did people even come up with the idea for service mesh?” then The Complete Guide to Service Mesh is for you.
If there is any trend that has created such a buzz in recent times, it has got be cloud computing. But does this mean that you should provide your software-plus-service from the cloud? Or should you tread with caution and wait for the market to stabilize? This paper attempts to provide Sanity-as-a-Service to ISV’s, Software-enabledbusinesses and Enterprises on cloud-enabling their software.
Transcript of a BriefingsDirect podcast on how a major telecom company has improved its IT performance to deliver better experiences and payoffs for its businesses and end users alike.
Use of free or cheap tools from SAAS and the cloud to support ITSM. There's a lot out there that can plug a hole if you can't afford the big expensive tool sets.
Presented at itSMFA August 2010.
Knowledge management in software architectureJon Cohn
Architectural knowledge has played a role in discussions on design, reuse, and evolution for over a decade. Over the past few years, the term has significantly increased in popularity and attempts are being made to properly define what constitutes ‘architectural knowledge’.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Designing Great Products: The Power of Design and Leadership by Chief Designe...
Microservices anti
1. MicroservicesAnti-patterns
Buzzwordsoftengive contexttoconceptsthatevolvedandneededagood“tag” to facilitate
dialogue.Microservices isanew“tag” that definesareasIhave personallybeendiscoveringand
usingforsome time now. ArticlesandconferencesdescribedsomethingthatI slowlyrealizedIhad
beenevolvinginmyownpersonal experience forthe pastfew years.
What it Was, Was Microservices
Buzzwordsoftengive contexttoconceptsthatevolvedandneededagood“tag” to facilitate
dialogue.Microservicesisanew“tag” that definesareasIhave personallybeendiscoveringand
usingforsome time now. ArticlesandconferencesdescribedsomethingthatI slowlyrealizedIhad
beenevolvinginmyownpersonal experience forthe pastfew years. While industryand
professionaldiscussionsonMicroserviceshave giventhe limelighttothe companieslike Netflix,
Amazon,andGoogle and to the practitionerswhohave done itsuccessfully,Ihave some personal
experience thatcanprovide insighttosuccessful Microservicesimplementation.
The three standardand most commonbusinessdriversforanyarchitecture are:
>ImprovedAgility –The abilitytorespondtothe businessneedsinatimelyfashionsothatthe
businesscangrow
>ImprovedCustomerExperience–Improve the customerexperience sothatcustomerchurn is
reduced
>DecreasedCost– reduce the costto add more products,customersor businesssolutions
In fact,all of us are tryingto do thisin our day-to-daywork.SOA createsabusinessalignedsoftware
frameworkthatenablesthe enterprisetogetthere.Several large software vendorshave emerged
and claimedthattheirsuite of productscan enable the enterprise todeliverSOA.
If you do nothave the rightpeople,culture,andinvestment,SOA will notdeliverthe businessvalue.
Microservicesarchitecture isnotfundamentallydifferentfromSOA,the goalsandobjectivesare the
same but the approach isslightlyrefinedandinfact,IwouldsimplysaythatMicroservicesismere
SOA made scalable.Microservicesenablesapplications/systemsthatdesperatelymustmove away
froma monolithicimplementation,toadistributed,decentralized,servicesplatformservingmany
applications.Microservicesare independentthatembrace agilityandapplicationevolutionasan
enterprise digitallytransform.Microservicessuccessdependsuponthe service independenceand
the service flexibility.
I woulddefine Microservicesas“Anapproach todeliveringSOA bybuildingfine-grainedservicesto
supportbusinesscapabilitiesthatare distributedandorganizedasfunctional domains".Nopattern
isa magicwand or silverbullet.Youshouldconceive andtailorthe patterncorrectlyforan
enterprise.Enterprisesshouldfocusonresolvingthe itemsthatare requiredtosupportthe
architecture tomake an adaptive platform.
A fewenterprisesfailedintheirSOA implementationmiserably–because theydid notfullyanalyze
theirbusinesscapabilitymodel andconsidereddevelopingweb-servicesmeanSOA orbuyingaSOA
2. suite fromlarge vendorwouldmake themSOA-enabledorthe inabilitytoshow the alignment
betweenSOA andtheirbusinessdriver/goals.
For Example
An example fromexperience mightclarifythispoint.Atone pastjob,the enterprise wasaimingto
improve agility,customerexperience anddrive downcost.We decidedtobuildastandardmulti-
tenantSOA platform.The approachwas setto developfine-grainedservicessothatwe couldmake
changesveryoftenanddeploysmall,manageable changestothe platform.If we didthe same
approach today,we wouldlikelycall itmicroservicesarchitecture.Backthenwe didnothave this
term,but itjustmade sense.
Serviceswere modeledbasedonbusinesscapabilitymodel andthe firstrelease wentwell.They
were XML overJMS syncservicesandprimarilyfocusedondeliveringthe capabilitiesrequiredfor
claimsplatformexposedtoAgents,webandvoice channel application.Itgave usthe abilityto
deployfrequent,small changesandA/Bfeature supportseamlesslyforourapplications.
Whenthe requirementswere incrementallyadded(andtheyalwayswere) itwasveryhardto
release the solutionrapidlybecause of the integrationcomplexitybetweenapplicationsandthe
consumers.Integration,functional testing,andproductionreleaserequiredtightcoordination.As
the businessstartedtoexpandandthe changeswere 10x more frequentthanthe initial release,and
as most of the tasks indeliverylifecyclewere manual,the time tomarketdidnotmeetbusiness
expectation.Soon,none of ourgoalswere metas poorMicroservicesautomationandlifecycle
managementledtodeliveryentropy.
LessonsLearned – Don’tDo These Things,Instead…DoThese OTHERThings
Thisbringsme to share some of the lessonsthatI learnedaspart of my journeysothat youcan keep
an eye onthese itemswhenyouhitthe roadwithMicroservices
1) CohesionChaos
We developedaservice togetthe customerinformationdesignedtopull the customerpolicy
information,personal informationandthe planthattheyenrolledin.Overatime,itstartedtodo
more than gettingthe customerinformation.Asnew requirementscame in,thisservicewent
throughfrequentchangesanddeployments.Itwasunable toscale and meetthe required
availability.Itbecame the proverbial “Bigball of mud”. How didit getthere?For starters,there was
no governance aroundfunctional separationof concern.If aninfluentialconsumeraskingtoput
unrelatedlogicinthisone service toreduce roundtrips,thatfunctiongotslappedonwithout
question. Perhapsagatewayora BPMlayercouldhave avoidedthisscenario,butthere wasnotime
for that…justtime tocrank out anotherbusinessfunctionpoint.
The preventative cure istogovernbusinessfunctionalitiesthatare notrelevanttothe service.
Servicesmustalignclearlytoabusinesscapabilityandshouldnottryto do somethingoutsideof
theirboundary.Functional separationof concernisvital forarchitecture togovernotherwiseitwill
destroythe agility,performance,andscalabilityandendedupinestablishingatightlycoupled
architecture,resultingindeliveryentropyandcohesionchaos.
3. 2) Not takingAutomationSeriously
We didn'thave a strategyfor automateddeploymentandopsmonitoringof services(runtime QoS
metrics).Itobviouslyincreasedoperational expensesandmanual errorsduringdeployment.Several
timesproductiondeploymentscausedoutages due toconfigurationerrors.The serviceswere always
deployedinHA mode andsothe numberof containerswas3x to the total numberof services.The
operationsteamwasunable tohandle the configurationforeachservice manually.Afteracertain
time,opsstartedto complainthatthe architecture wasinefficientastheywere notable tohandle
the increasednumberof containers.
What isthe vaccine forthis?The recipe has multipleingredients. Continuousdeployment,if you
have not done so,isa mustinvestmentanda cultural change that everyenterprise shouldaimfor.
At least,if youdon'thave a wayto automaticallytestanddeploy –do notdo micro-services.
Microservicesare aimingtodrive agility,withthe speedwe needtochange;qualityassurance
involveseachservicehavingautomatedunit,functional,securityandperformance testing.Service
Virtualizationisanotherpowerful conceptwhenwe developservicesthatare integratedwith
servicesoutside of ourcontrol.
3) LayeredServicesArchitecture
One commonmistake people made withSOA weremisunderstandinghow toachieve the re-
usabilityof services.Teamsmostlyfocusedontechnical cohesionratherthanfunctionalregarding
reusability.Forexample,several servicesfunctionedasadata access layer(ORM) to expose tablesas
services;theythoughtitwouldbe highlyreusable.Thiscreatedanartificial physical layermanaged
by a horizontal team,whichcauseddeliverydependency.Anyservice createdshouldbe highly
autonomous – meaningindependentof eachother.
Creatingmultiple,technical,physical layersof serviceswouldonlycause deliverycomplexityand
runtime inefficiency.We endedupinhavingwrapperservices,orchestrationservices,business
servicesanddataservices.These servicemodelsservedtechnical concerns.Individual teamsformed
to manage these layersandendeduphavingbusinesslogicsprawl,nosingleownerfora capability,
lostthe efficiencyandthere wasalwaysablaminggame.
Logical separationof layerswithina service isfine,however,thereshouldnotbe anyoutof process
calls.Try to lookat a service asone atomic businessentity,whichmustimplementeverythingto
achieve the desiredbusinessfunctionality.The self-containedservicesare more autonomousand
scalable thanthe layeredservices.It'sperfecttore-write some commoncode acrossmultiple
services,that'sfine andit'sa good trade-off tokeepthe autonomylevel.The bottomline isthat
don't have servicesseparatedbytechnical concernsinstead theymustbe separatedbasedonthe
businesscapability.The conceptof containerizationisthrivingbecause of thischaracter.
4) RelyingonConsumerSign-off
We hada service consumedbymultipleapplicationsfromthree differentchannelsi.e.agent,the
web,andvoice.Agentchannel wasourprimary,sothe serviceshadtowaitto get theirsign-off
before theycango intoproduction.Itdelayedthe voice andwebapplicationproductionreleases.
What boundthose three channelstogethersotightly?
4. The service wasnot a looselycoupledwhenitcame tochannel specificfunctionality.Give
independencetoyourservices.Everyservicethatyoudelivermusthave a testsuite,whichshould
coverall the service functionality,security,performance,errorhandling,andconsumptiondriven
testingforeverycurrentandfuture consumer.Thismustbe includedaspart of the buildpipeline for
automatedregressiontesting.
5) Manual ConfigurationsManagement:
As we startedto doa largernumberof services(andthe inevitablesprawl due tolackof service
lifecycle governance manifesteditself) managingthe configurationsforeachservice wentoutof
control.Most of ourproductiondeploymentwasnotsmoothbecause of configurationfailureslike
the bad password,wrongURL, incorrectvalues.Itbecame harderandharder to manage these
manually.If we hadonlyusedapplicationconfigurationmanagementtoolsaspartof a PaaS or
CD…but we didn’t.
6) VersioningAvoidance:
Naively,we thoughtitwouldbe onlyneedone versionof the service.Thenwe startedtoaddmajor,
minorversionstoaccommodate multiple consumersandfrequentchanges.Eventually,every
release hadtobe a majorrelease since the serviceswere relyingonconsumersignoff.Asa result,
the numberof containersincreasedveryfastanditbecame a huge painto manage them.Lack of
runtime governance wasanotheraspectthatcontributedtothisissue.Some enterprisesfoolishlytry
to avoidversioning.Servicesneedtobe architectedassumingthatchange isinevitable. Have a
strategyto manage the forwardcompatible servicechangesandallow yourconsumerstoupgrade
gracefully.Otherwise,itwillleadtohaving consumerstightlyboundtoaservice versionandbreak
whenthere isa change.
The complexitygrowsasthe numberof servicesgrowswhichthe microservicesworldexpects.Have
a versioningstrategythatcanallowthe consumersagraceful migrationandassure providerscan
transparentlydeploychangeswithoutaffectinganyone.Limitthe numberof side-by-sidemajor
versionsinthe productionandgovernthem.
7) Buildingagatewayineveryservice
We didn'thave an APIgatewayandwe didn'thave runtime governance (we didn’tknow whowas
consumingwhatandat whatrate at whattime).We startedto implementend-userauthentication,
throttle,orchestrate,transform, androute etc.ineachservice.Itaddedcomplexitytoeachservice
and we lostconsistencyof implementationfromservice toservice,sowe hadno ideawho
implementedwhatandwhere.Ontopof it,some of our serviceswere builttosatisfyone consumer
non-functional requirements,butnotanother’s.If we hada gateway,applyingsome datafiltering
and enrichmentpatternscouldhave done it.If only.
InvestinAPIManagementsolutionstocentralize,manage andmonitorsome of the non-functional
concernsand whichwouldalsoeliminate the burdenof consumer'smanagingseveral microservices
configurations.APIgatewaycanbe usedorchestrate the cross-functional microservicesthatmay
reduce roundtripsfor webapplications.
5. Conclusion
The goal of microservicesistosolve the three mostcommonproblemsi.e.improvecustomer
experience, highlyagile tothe newrequirementsanddrive downcostbydeliveringthe business
functionsasfine grainedservices.Thisisnota silverbulletandrequiresadisciplinedplatform,
where deliveringthe servicesinanagile fashionwithhighqualityispossible.Learnfromother’s
mistakes(mine) andavoidthe above listedpatternsinthe architecture anddeliveryprocess.Thisis
the firstbaby stepbefore we caneventalkaboutcontainerization,cloudadoptionetc.Ihope this
article givesyousomethingtothinkaboutforyour enterprise andworktowardsresolvingtheseanti-
patternsbefore youweave themintoyourarchitectures.Mostof the itemswill drive cultural
changeswithinthe organizationandcannotbe done justbyyourself,ensurepartnershipwithyour
executiveandseniorleaders.
Source : infoq.com
Recommendedby:
JonCohn ,CTO, VP IT Architecture
https://www.linkedin.com/in/jonacohn
joncohn@comcast.net
"JonCohn ExtonPA""JonCohn Exton""JonCohnEvolution"